Trap Radar Bot v2 is out. One bot can now hold several strategies for Long and for Short. Each strategy has its own entry conditions, coin filter, entry size and position limit.
In the first version, a second trading idea meant creating a second bot. In v2 you add a strategy instead.
What’s new
- several strategies per side in one bot;
- each strategy has its own entry conditions, coin filter, first entry size and position limit;
- strategies are switched on and off individually, without stopping the bot;
- logs and stats for every strategy, including deleted ones;
- a safety stop after every averaging queue;
- export and import of the full config, single strategies and Trap Radar PRO conditions.
Why several strategies
In the first Trap Radar Bot each side had one set of entry rules, and the entry size and position limit applied to the whole side.
Say you want to short sharp pumps on small coins with a small size, and short overheated large caps with a bigger size and a different limit. The conditions, coin lists and position sizes differ, so both setups don’t fit into one rule set.
Before, the second setup needed a second bot, which meant a new exchange subaccount and new API keys. In v2 they are two strategies in one bot.
What a strategy contains
A strategy belongs to one side, Long or Short. It has:
- a name;
- an on/off switch, applied immediately;
- first entry size: a fixed USDT amount or a percentage of the wallet;
- a position limit;
- entry conditions based on indicators;
- the market whose data is used to check conditions: Bybit, Binance or combined;
- a per-ticker pause: how often the same coin can pass into the strategy, once every 900 seconds by default;
- a coin filter: 24h volume, coin age, price change over a period, funding rate and interval, exchange labels (copy trading, innovation zone, stocks and ETFs, ST);
- repeat DCA: adding to an open position when the strategy’s conditions match that coin again.
[IMAGE: strategy-editor.png — strategy editor: position size and entry conditions]
Entry conditions
Conditions use eight groups of metrics: RSI, VWAP deviation, open interest, market pulse, price, liquidations, volume spike and CVD. Timeframes range from 5 minutes to 1 day.
A condition is a threshold or a range, for example RSI ≥ 70 or RSI from 65 to 75. With the range, a value of 70 passes and 60 or 80 does not.
Each condition is marked as required (AND) or optional (OR). All required conditions must be met. For optional ones you set a minimum number of matches, for example two of four.
Market pulse is calculated across the whole market: median RSI, share of assets above SMA200, median deviation from regression. You can use it, for example, to allow entries only when the market as a whole is overheated.
Position limit
The limit is set in each strategy. It counts all of the bot’s positions on the strategy’s side, whichever strategy opened them. Positions on the other side are not counted.
Example: the bot has 5 shorts and 7 longs open. A SHORT strategy with a limit of 5 makes no new entries, a SHORT strategy with a limit of 10 can still enter. The longs don’t affect this.
Repeat DCA and its cap
Repeat DCA is switched on per strategy. If the strategy’s conditions match again on a coin with an open position, the bot adds to it.
You can set a maximum position size in USDT for these add-ons. Example: the cap is 100 USDT, the position holds 8 coins, the new order is for 3 coins, the average price is 10 USDT. After the add-on the position would be (8 + 3) × 10 = 110 USDT. That exceeds the cap, so the whole order is skipped.
Repeat DCA and queue averaging are switched on independently.
Shared side settings
Strategies only handle entries. Everything else is set for the whole side:
- take profit, trailing stop, safety stop and smart take, separately for bull, neutral and bear markets;
- averaging queues;
- margin usage thresholds at which the bot stops new entries, averaging, repeat DCA or all trading;
- coin whitelist and blacklist.
Averaging now has a safety stop for each queue. It is placed after the queue fills, if the position is in profit, at a set distance from the average entry price, and stays fixed.
Log and stats
A strategy card shows how many times its conditions matched and how each case ended: entry, skip or error. Data covers 24 hours, 7 days, 30 days and all time.
The bot log can be filtered by strategy, status, action, side and ticker. New entries and repeat DCA are counted separately. History of deleted strategies is kept.
Moving settings
Bot settings can be exported to a file and imported into another bot. You can move the full config, single strategies and compatible Trap Radar PRO conditions.
Before importing you see which settings will be replaced. Old strategies are archived with their history, imported ones are added switched off. API keys are not included in the file.
How to start
1. Open My bots and create a bot of the Trap Radar Bot V2 type.
2. Choose the exchange: Bybit or Binance.
3. Connect API keys of a new subaccount with no trading history. Withdrawal permission is not needed.
4. Choose demo trading (Bybit only) or a real account.
5. Create a strategy, then set up closing and averaging for the side.
6. Run the Crypto Resources app on Windows or a Linux server. The app executes trades and manages positions.
Pricing
There is no bot subscription. A commission is charged only on a positive trade result: 25% base rate, 20% for Bybit partners, lower with a premium status.
FAQ
How is Trap Radar Bot v2 different from the first version?
In v2 one bot can hold several strategies per side, each with its own entry conditions, coin filter, size, position limit, per-ticker pause and repeat DCA. Closing, averaging and margin thresholds are shared per side.
How many strategies can I create?
Several for Long and several for Short. The current limit is shown on the Entry strategies page.
How is a strategy’s position limit counted?
It counts all of the bot’s positions on the strategy’s side, opened by any strategy. Positions on the other side are not counted.
Which exchanges does the bot support?
Bybit and Binance. Entry conditions can be checked against Bybit, Binance or combined data.
Can I bring conditions over from Trap Radar PRO?
Yes, compatible Trap Radar PRO conditions can be imported into a bot strategy.
Is there a demo mode?
Yes, on Bybit.
Does the bot need withdrawal access?
No. Funds stay on the exchange, and the API is used only for trading operations.
Risk disclaimer
This material is for information only and is not investment advice. Trap Radar Bot automates the rules you set and does not guarantee profit. Leveraged futures trading carries a high risk of loss. Test your settings in demo mode before trading on a real account.