Settings reference / Risk & safety
Risk & safety settings
Loss caps and limits, position caps, liquidation buffers, the correlation guard, slippage and the key/connection guard. 34 settings on this tab.
Generated from the code. Defaults, ranges, choices, units and the live confirmation rule on this page are read from the settings schema each time the docs are generated, so they always match the bot.
Summary
All settings
Total loss cap
safety_total_loss_usdt I ACCEPT in live
- Default
- 5 USDT
- Range
- 0 to 1e+06 USDT
- Type
- Number
- Unit
- USDT
- Live confirmation
- Yes: raising it in live mode asks you to type I ACCEPT.
In the dashboard: Live: when the realized loss since the count started reaches this, no new trades are opened and a high-priority notification is sent. It waits for you. 0 = off (no total cap; the daily cap and the balance floor still apply).
What it does
Live safety. When the realized loss since the count started reaches this, no new trades are opened, a critical notification is sent, and the bot waits for you. Open positions keep their stops. 0 switches it off (no total cap); the daily loss cap and the balance floor (min_balance_floor_usdt) still apply.
Example
Cap 5 USDT. Since the count started you closed trades at -3, +1 and -3 USDT: net -5, so new trades stop. After reviewing, press "Count losses from now" on the Live learning page, or raise the cap.
When to change it
Set it to the most you are willing to lose before you look at what happened. Applies in testnet too if safety_in_testnet is on.
Higher, lower, on or off
Higher: more total loss is allowed before the bot stops opening trades. Lower: it stops sooner. 0: no total cap.
Risk notes
High if raised carelessly or switched off: it is a last line of defence on real money; with 0, set a balance floor instead. Wins offset losses in the count (it uses net realized PnL in the current mode). Raising it or switching it off needs I ACCEPT in live.
Daily loss cap
safety_daily_loss_usdt I ACCEPT in live
- Default
- 2 USDT
- Range
- 0.1 to 1e+06 USDT
- Type
- Number
- Unit
- USDT
- Live confirmation
- Yes: raising it in live mode asks you to type I ACCEPT.
In the dashboard: Live: when today's (UTC) realized loss reaches this, no new trades until tomorrow. Cannot be switched off.
What it does
Live safety. When today's realized loss (UTC day) reaches this, no new trades are opened until the next UTC day. A critical notification is sent. It cannot be switched off in live mode.
Example
Cap 2 USDT. Today (UTC) you closed trades at -1.20 and -0.90 USDT: -2.10, so new trades stop until 00:00 UTC. Open positions keep their stops.
When to change it
Set it to the most you accept losing in one day. Applies in testnet too if safety_in_testnet is on.
Higher, lower, on or off
Higher: more loss per day before the pause. Lower: the bot pauses sooner on a bad day.
Risk notes
High if raised carelessly. The day follows UTC, not your local time.
Allow resetting today's loss count
daily_loss_reset_button
- Default
- On
- Range
- On or off
- Type
- On/off
- Live confirmation
- No. Changes apply in every mode without the typed confirmation.
In the dashboard: A 'Reset today's loss count' button next to the loss caps: today's count for the daily cap starts again from zero (live: type I ACCEPT). The cap values never change; recorded in History and notified.
What it does
Allows the 'Reset today's loss count' button next to the live safety loss caps. A reset makes today's count for the daily cap start again from zero, so new entries are allowed again today if the daily cap was the only thing stopping them. It never changes the cap values or the total count, never lifts a manual pause, is recorded in History and sends a notification. In live mode you must type I ACCEPT.
Example
On: the daily cap is 2 USDT and today's losses reached -2.31 USDT, so entries stopped at 14:00. You press the button and type I ACCEPT: the count shows 0.00 and entries resume; a further -2.00 USDT today would stop them again. The total cap still counts the -2.31.
When to change it
Turn it off if you never want today's count to be reset early.
Higher, lower, on or off
On: you can let the bot trade again the same day after reviewing the losses. Off: the button and the reset request are refused.
Risk notes
Medium: each reset allows up to one more daily cap of losses that day. The total cap still applies.
Balance floor
min_balance_floor_usdt I ACCEPT in live
- Default
- 0 USDT
- Range
- 0 to 1e+09 USDT
- Type
- Number
- Unit
- USDT
- Live confirmation
- Yes: lowering it in live mode asks you to type I ACCEPT.
In the dashboard: Live: no new trades while the futures wallet balance (USDT, realized, without open positions' unrealized PnL) is below this; a high-priority notification is sent when it triggers. Entries resume by themselves once the balance is back at or above it. Open positions keep their stops. 0 = off.
What it does
Live safety. While the futures wallet balance (USDT, realized: without the unrealized PnL of open positions) is below this, no new trades are opened. When it triggers a critical, high-priority notification is sent. Entries resume by themselves once the balance is back at or above the floor (for example after a deposit). Open positions keep their stops and are managed as usual. 0 = off.
Example
Floor 40 USDT, wallet balance 41.20. A stop-out of -1.50 brings it to 39.70: new trades stop and "TRADING STOPPED: balance floor reached" is sent. A deposit of 5 USDT (44.70) lets entries resume within a minute.
When to change it
Set it to the balance you never want trading to go below, especially when the total loss cap is off.
Higher, lower, on or off
Higher: trading stops sooner as the balance falls. Lower: later. 0: no floor.
Risk notes
High if lowered or switched off carelessly (needs I ACCEPT in live). The balance is read about every 30 seconds, so a fast loss can go slightly below the floor before entries stop; open positions are never closed by it.
Balance cap for sizing
safety_balance_cap_usdt I ACCEPT in live
- Default
- 0 USDT
- Range
- 0 to 1e+09 USDT
- Type
- Number
- Unit
- USDT
- Live confirmation
- Yes: raising it in live mode asks you to type I ACCEPT. Setting it to 0 (no limit) counts as raising it.
In the dashboard: Live: sizing uses the smaller of the available balance and this cap, so money you deposit for manual trading does not make the bot's trades bigger. 0 = no cap (the whole available futures balance, read from the exchange on every trade).
What it does
Live safety. Sizing uses the smaller of the sizing base (available balance, plus own pending entries if sizing_base says so) and this cap, so money you deposit for manual trading does not make the bot's trades bigger. 0 means no cap.
Example
Available 300 USDT, cap 50 USDT, margin_pct 10%: sizing uses 50 USDT, so margin is 5 USDT per entry instead of 30 USDT.
When to change it
Set it when the futures account holds more money than you want the bot to size from, for example funds for your own trades.
Higher, lower, on or off
Higher: larger trades allowed, up to the real balance. Lower: smaller trades. 0: the whole available futures balance, read from the exchange on every trade.
Risk notes
High if raised or set to 0 on a big account: every new deposit then grows the bot's trade size. Applies only in live (and testnet with safety_in_testnet).
Apply the live safety in testnet too
safety_in_testnet
- Default
- Off
- Range
- On or off
- Type
- On/off
- Live confirmation
- No. Changes apply in every mode without the typed confirmation.
In the dashboard: The loss caps and the balance cap also apply in testnet mode.
What it does
Applies the two loss caps and the balance cap in testnet mode too. In live they always apply; in paper they never do.
Example
On, with the daily cap at 2 USDT: if testnet trades lose 2 USDT today (UTC), testnet stops opening new trades until tomorrow, just as live would.
When to change it
Turn it on to rehearse exactly how the live limits will behave before going live.
Higher, lower, on or off
On: testnet behaves like live for the caps and balance cap. Off: testnet ignores them.
Risk notes
Low: testnet uses no real money.
Buffer before liquidation
liq_buffer_pct_of_margin I ACCEPT in live
- Default
- 8 % of margin
- Range
- 0.5 to 50 % of margin
- Type
- Number
- Unit
- % of margin
- Live confirmation
- Yes: lowering it in live mode asks you to type I ACCEPT.
In the dashboard: Wall hug. The stop's fill (after paper slippage) must sit at least this much of margin before the liquidation price, or liq_min_ticks, whichever is larger, plus the learned safety offset. Near-liquidation stops are placed exactly there.
What it does
Wall hug safety gap. The stop's fill price (after the assumed slippage) must sit at least this share of margin before the liquidation price, or liq_min_ticks, whichever is larger, plus a learned safety offset. In near_liquidation mode the stop is placed exactly at this gap.
Example
50x BTC long at 60000: 8% of margin is a price move of 8% / 50 = 0.16%, which is 96 USDT. 10 ticks is 1 USDT, so the gap is 96 USDT. If the slipped stop fill is closer than that to liquidation, the bot tries a lower leverage.
When to change it
Raise it for more safety margin against liquidation estimate errors. Lower it only if you understand the trade-off.
Higher, lower, on or off
Higher: lower leverage chosen, more distance between stop and liquidation. Lower: higher leverage possible, less room for error.
Risk notes
High: this is a core protection against liquidation before the stop fills. In live mode, after the fill the bot also compares the stop with Binance's own liquidation price using this buffer.
Plan with the observed stop slippage
observed_slippage
- Default
- On
- Range
- On or off
- Type
- On/off
- Live confirmation
- No. Changes apply in every mode without the typed confirmation.
In the dashboard: Wall hug: plan leverage and the liquidation buffer with a high percentile of this coin's actual live stop-fill slippage (once it has enough fills), never less than paper_slippage_bps. Entry and stop placement are unchanged; the value used is logged per trade.
What it does
Plans each wall-hug trade's leverage and its buffer before liquidation with the stop slippage that actually happens on that coin: a high percentile (observed_slippage_pct, p90) of its live stop fills, once there are at least observed_slippage_min_samples of them. Until then, and never less, it uses paper_slippage_bps (5 bps). Where the entry and stop go does not change; only how much leverage still keeps the slipped stop fill safely before liquidation. The value used is written in the 'Wall hug at ...' log line and stored with the trade.
Example
On: ETHUSDT has 6 live stop fills with slippage 0, 1, 2, 3, 4 and 9.8 bps, so p90 = 9.8 bps. A short with the stop 0.40% behind the wall is planned as if the stop fills 9.8 bps late: 105x no longer keeps 8% of margin before liquidation, so the planner picks about 95x.
When to change it
Leave it on. Turn it off to go back to the fixed paper_slippage_bps for every coin.
Higher, lower, on or off
On: lower leverage on coins whose stops slip a lot, more room before liquidation. Off: the same 5 bps for every coin.
Risk notes
Low: slightly smaller positions on fast coins. Off can leave too little room before liquidation when a stop slips.
Observed slippage percentile
observed_slippage_pct
- Default
- 90 %
- Range
- 50 to 100 %
- Type
- Number
- Unit
- %
- Live confirmation
- No. Changes apply in every mode without the typed confirmation.
In the dashboard: Which percentile of the coin's live stop-fill slippage is planned with.
What it does
The percentile of a coin's live stop-fill slippage used for planning (see observed_slippage).
Example
At 90: with 10 fills the second-worst one is used; at 100 the worst fill ever seen.
When to change it
Raise it to plan for the worst cases; lower it for typical fills.
Higher, lower, on or off
Higher: more conservative leverage. Lower: closer to the average slippage.
Risk notes
Low.
Observed slippage: minimum fills
observed_slippage_min_samples
- Default
- 5
- Range
- 1 to 1000
- Type
- Whole number
- Live confirmation
- No. Changes apply in every mode without the typed confirmation.
In the dashboard: Live stop fills a coin needs before its own slippage is used; until then paper_slippage_bps.
What it does
How many live stop fills a coin needs before its own slippage is used; until then the bot plans with paper_slippage_bps.
Example
At 5: a coin with 3 stop fills still uses 5 bps; from the 5th fill on, its p90.
When to change it
Raise it if a few unusual fills should not change the plan.
Higher, lower, on or off
Higher: slower to adapt. Lower: adapts after fewer fills.
Risk notes
Low.
Minimum ticks before liquidation
liq_min_ticks I ACCEPT in live
- Default
- 10 ticks
- Range
- 0 to 1000 ticks
- Type
- Whole number
- Unit
- ticks
- Live confirmation
- Yes: lowering it in live mode asks you to type I ACCEPT.
In the dashboard: Wall hug. The stop's fill must sit at least this many ticks before liquidation.
What it does
Wall hug safety gap in ticks: the stop's fill must sit at least this many ticks before liquidation. The larger of this and liq_buffer_pct_of_margin wins. Also used when checking positions found on the exchange at startup.
Example
BTC tick 0.1, 10 ticks = 1 USDT. At 50x, 8% of margin is 96 USDT, so the percentage buffer decides. On a coin with a coarse tick, 10 ticks can be the larger value.
When to change it
Raise it on coins with large ticks or jumpy prices.
Higher, lower, on or off
Higher: more distance in ticks to liquidation, sometimes lower leverage. Lower: the percentage buffer alone usually decides.
Risk notes
Medium: a floor on the liquidation gap; lowering it reduces safety on coarse-tick coins.
Max fees
max_fee_pct_of_margin I ACCEPT in live
- Default
- 15 % of margin
- Range
- 1 to 100 % of margin
- Type
- Number
- Unit
- % of margin
- Live confirmation
- Yes: raising it in live mode asks you to type I ACCEPT.
In the dashboard: Wall hug. The leverage picker steps down until the round-trip fees (maker entry + taker exit) are at most this share of margin.
What it does
Wall hug leverage limit based on fees. The leverage picker steps down until round-trip fees (maker entry plus taker exit, on the full position) are at most this share of margin.
Example
Maker 0.02% plus taker 0.05% = 0.07% per round trip. At 125x that is 8.75% of margin, under 15%, so it passes. With the setting at 5%, the highest allowed leverage is 71x (4.97%).
When to change it
Lower it if fees eat too much of each trade. On standard Binance fees the default rarely limits leverage.
Higher, lower, on or off
Higher: allows higher leverage even when fees are a large part of the margin. Lower: caps leverage so fees stay a smaller share.
Risk notes
Medium: higher values allow trades where fees take a big share of margin.
Max added margin (live)
max_added_margin_pct I ACCEPT in live
- Default
- 50 % of margin
- Range
- 0 to 200 % of margin
- Type
- Number
- Unit
- % of margin
- Live confirmation
- Yes: raising it in live mode asks you to type I ACCEPT.
In the dashboard: Live only. If Binance's liquidation price turns out closer than our estimate and the stop is no longer safely before it, the bot adds isolated margin once per trade, at most this share of the original margin. Binance's auto-add-margin feature is never switched on.
What it does
Live only. After the stop is placed, the bot compares it with Binance's own liquidation price. If the stop is no longer safely before it, the bot adds isolated margin once per trade, at most this share of the original margin. If that is still not enough, it moves the stop inward, or closes the trade if the stop would end up in front of the wall.
Example
Trade margin 10 USDT, setting 50: up to 5 USDT can be added. If 3 USDT would move liquidation far enough, 3 USDT is added. 0 never adds margin.
When to change it
Lower it (or 0) if you never want extra money put into a trade.
Higher, lower, on or off
Higher: more chances to keep the planned stop when Binance's liquidation is closer than estimated. Lower: more trades get a tighter stop or an emergency close instead.
Risk notes
Medium: it puts more money at risk on that trade. Binance's auto-add-margin feature is never switched on.
Liquidation cushion
liq_cushion_pct
- Default
- 0.3 % of price
- Range
- 0.05 to 5 % of price
- Type
- Number
- Unit
- % of price
- Live confirmation
- No. Changes apply in every mode without the typed confirmation.
In the dashboard: Minimum gap between the stop and the estimated liquidation price.
What it does
Minimum gap between the stop and the estimated liquidation price, as a share of price. A plan whose stop is closer to liquidation is refused (in auto leverage, the next lower leverage is tried). Used by the loss budget model and by wall hug with stop_mode wall_ticks.
Example
A long's estimated liquidation is 98.00. With 0.30% the stop must be above 98.00 x 1.003 = 98.294, so a stop at 98.25 is refused.
When to change it
Raise it for more safety margin on volatile coins. Lower it only if you understand that the stop may then fill very near liquidation.
Higher, lower, on or off
Higher: more room between stop and liquidation, so lower leverage or fewer valid plans. Lower: higher leverage passes, but a slipped stop can come close to liquidation.
Risk notes
High when lowered. Wall hug's other stop modes use their own liquidation buffer checks instead of this one.
Max open trades
max_positions I ACCEPT in live
- Default
- 3
- Range
- 1 to 20
- Type
- Whole number
- Live confirmation
- Yes: raising it in live mode asks you to type I ACCEPT.
In the dashboard: Pending entries count toward this limit.
What it does
The most trades Wallbot holds at once. Pending entries and open positions both count. When the limit is reached, no new entry is placed until one closes or is cancelled. Movers coins also have their own smaller limit.
Example
At 3: with 2 open positions and 1 pending entry, a new wall is skipped. When the pending entry times out, the next wall can be traded.
When to change it
Raise it to use more of the balance across coins. Lower it to limit total exposure.
Higher, lower, on or off
Higher: more trades at once, more total margin at risk. Lower: fewer simultaneous trades and less total risk, but more walls go unused.
Risk notes
High when raised: several stop-outs can happen together, each costing a share of margin_pct.
Correlation threshold
correlation_threshold I ACCEPT in live
- Default
- 0.8
- Range
- 0 to 1
- Type
- Number
- Live confirmation
- Yes: raising it in live mode asks you to type I ACCEPT.
In the dashboard: Pairwise correlation of 15m returns above which two coins count as correlated.
What it does
The correlation of 15m returns above which two coins count as correlated for max_same_direction_correlated. 1.0 means they always move together; 0 means no relation.
Example
At 0.8: BTC and ETH at 0.86 count as correlated; BTC and a small coin at 0.55 do not.
When to change it
Lower it to treat more coin pairs as related (stricter guard). Raise it to block only very closely linked coins.
Higher, lower, on or off
Higher: fewer pairs count as correlated, so fewer entries are blocked. Lower: more pairs count, so more entries are blocked.
Risk notes
Moderate when raised: near 1.0 the guard almost never triggers.
Correlation window
correlation_days
- Default
- 7 days
- Range
- 1 to 14 days
- Type
- Whole number
- Unit
- days
- Live confirmation
- No. Changes apply in every mode without the typed confirmation.
In the dashboard: Days of 15m candles used for the correlation (refreshed hourly).
What it does
How many days of 15m candles are used to measure correlation for the correlation guard. The data is refreshed about once an hour for the watched coins and coins with trades.
Example
At 7: the bot loads 7 x 96 + 1 = 673 fifteen-minute candles per coin and correlates their returns.
When to change it
Lower it to react faster to changing market behaviour. Raise it for a steadier measure.
Higher, lower, on or off
Higher: a slower, steadier correlation that ignores short episodes. Lower: follows recent behaviour more closely but jumps around more.
Risk notes
Low. Only changes which entries the correlation guard blocks. Not used when max_same_direction_correlated is 0.
Daily loss limit
daily_loss_limit_pct I ACCEPT in live
- Default
- 10 % of balance
- Range
- 1 to 100 % of balance
- Type
- Number
- Unit
- % of balance
- Live confirmation
- Yes: raising it in live mode asks you to type I ACCEPT.
In the dashboard: Halt new entries once today's realised loss reaches this share of the day's starting balance.
What it does
Once today's realised loss reaches this share of the day's starting balance, new entries are paused and all pending entries are cancelled. Open positions keep their stops. The pause lifts at the next UTC day, or when you resume.
Example
At 10% with a day's starting balance of 200 USDT: when today's closed trades add up to -20 USDT, entries stop for the rest of the UTC day.
When to change it
Lower it to stop sooner on a bad day. Raise it only if you accept larger daily drawdowns.
Higher, lower, on or off
Higher: the bot keeps trading through bigger losing days. Lower: it pauses sooner, limiting the day's loss.
Risk notes
High when raised. Only realised losses count, so an open losing position can push the day past the limit when it closes.
Paper stop slippage
paper_slippage_bps
- Default
- 5 bps
- Range
- 0 to 200 bps
- Type
- Number
- Unit
- bps
- Live confirmation
- No. Changes apply in every mode without the typed confirmation.
In the dashboard: Simulated slippage on stop and market exits in paper mode.
What it does
Simulated slippage on stop and market exits in paper mode and backtests (1 bps = 0.01%). It is also the slippage assumption in planning: wall hug's liquidation and loss checks, the breakeven stop, and the live-test slippage comparison use it in every mode.
Example
At 5 bps: a paper long stopped at 100.00 fills at 99.95. At 50x that extra 0.05% costs 2.5% of margin.
When to change it
Raise it if real stop fills are worse than this, so paper results and safety checks are more realistic.
Higher, lower, on or off
Higher: paper exits fill worse, plans keep more room before liquidation, and breakeven stops sit a bit further in profit. Lower: more optimistic paper results and tighter safety margins.
Risk notes
Moderate. Setting it too low makes paper results look better than live, and narrows the liquidation safety room in live planning.
Foreign margin warning: USDT
foreign_margin_warn_usdt
- Default
- 1 USDT
- Range
- 0 to 1e+06 USDT
- Type
- Number
- Unit
- USDT
- Live confirmation
- No. Changes apply in every mode without the typed confirmation.
In the dashboard: Warn about margin used by positions or orders the bot did not open when it exceeds the larger of this and the % below.
What it does
Testnet and live: the bot works out how much margin is used by positions or orders it did not open ("foreign" margin). It shows a dashboard warning and logs it when foreign margin is above the larger of this amount and foreign_margin_warn_pct of the balance. Only the warning changes; sizing is not affected by this setting.
Example
1 USDT and 1% with a 500 USDT balance: the threshold is the larger of 1 and 5, so 5 USDT. Foreign margin of 3 USDT shows nothing; 8 USDT shows the warning. With a 50 USDT balance the threshold is 1 USDT.
When to change it
Raise it if you deliberately trade manually on the same account and do not want the banner. Keep it low on an account used only by the bot.
Higher, lower, on or off
Higher: the warning appears only for larger foreign use. Lower: even small foreign use is flagged. 0 together with 0%: any foreign margin is flagged.
Risk notes
Low. Display only, but a high value can hide a forgotten manual position.
Foreign margin warning: % of balance
foreign_margin_warn_pct
- Default
- 1 %
- Range
- 0 to 100 %
- Type
- Number
- Unit
- %
- Live confirmation
- No. Changes apply in every mode without the typed confirmation.
In the dashboard: See above.
What it does
The percentage part of the foreign-margin warning. The warning shows when margin used by positions or orders the bot did not open is above the larger of foreign_margin_warn_usdt and this percentage of the balance.
Example
1% with a 2,000 USDT balance and foreign_margin_warn_usdt at 1: the threshold is the larger of 1 and 20, so 20 USDT. Foreign margin of 15 USDT shows nothing; 25 USDT shows the warning.
When to change it
Raise it on a shared account with regular manual trades. Lower it to catch any outside activity.
Higher, lower, on or off
Higher: larger foreign use is tolerated before warning, mainly on big balances. Lower: smaller foreign use is flagged.
Risk notes
Low. Display only.
Check the coin's actual leverage before every entry
verify_leverage_before_entry
- Default
- On
- Range
- On or off
- Type
- On/off
- Live confirmation
- No. Changes apply in every mode without the typed confirmation.
In the dashboard: Before every entry, re-place and re-plan, read the coin's actual leverage setting on Binance. If it differs from the plan, set the planned leverage; if Binance refuses or allows less, the entry is not placed and the next evaluation plans with the leverage Binance allows. A change made outside Wallbot is notified.
What it does
Before every entry, re-place and re-plan, Wallbot reads the coin's ACTUAL leverage setting on Binance (the same symbolConfig read as the isolated-margin check, so no extra request). If it differs from the plan, Wallbot sets the planned leverage. If Binance refuses or allows less, the entry is not placed and the next evaluation plans with the leverage Binance allows (margin, liquidation and every check recomputed). A change Wallbot did not make is logged and notified: "leverage on LTCUSDT changed outside Wallbot: 75x → 10x". The leverage is never changed under Wallbot's own resting order or open position on the coin.
Example
Wallbot set LTCUSDT to 75x; someone sets it to 10x in the Binance app. At the next LTC entry Wallbot reads 10x, notifies, sets 75x again and places the order with 2 USDT margin instead of Binance reserving 15 USDT at 10x.
When to change it
Keep it on. Turn it off only for testing.
Higher, lower, on or off
On: every order is placed at the leverage it was planned for. Off: Wallbot trusts the leverage it last set.
Risk notes
Off: an outside leverage change makes Binance reserve much more margin than planned, blocking other entries.
Alert when reserved margin exceeds the plan by
margin_reserve_alert_pct
- Default
- 20 %
- Range
- 0 to 500 %
- Type
- Number
- Unit
- %
- Live confirmation
- No. Changes apply in every mode without the typed confirmation.
In the dashboard: High-priority alert when the margin Binance holds for Wallbot's orders and positions on a coin is more than this much above the planned margin (e.g. a leverage change re-margined them). 0 = off.
What it does
A high-priority alert when the margin Binance holds for Wallbot's orders and positions on a coin is more than this percentage above the margin Wallbot planned (for example after a leverage change re-margined them). The alert names the coin, both amounts and both leverages; nothing is cancelled or closed. 0 turns it off.
Example
A short entry planned with 2.00 USDT at 75x; Binance holds the coin at 10x and reserves 15.00 USDT (+650%): above 20%, so a "MARGIN LTCUSDT: 15.00 reserved vs 2.00 planned" alert goes out (at most once per coin per hour).
When to change it
Lower it to catch smaller differences; raise it if price moves on open positions trigger it.
Higher, lower, on or off
Lower: more sensitive. 0: no alert.
Risk notes
Low. It only alerts.
Reserved-margin check every
margin_check_interval_s
- Default
- 60 s
- Range
- 10 to 3600 s
- Type
- Whole number
- Unit
- s
- Live confirmation
- No. Changes apply in every mode without the typed confirmation.
In the dashboard: How often the margin Binance reserves is compared with the plan while Wallbot has orders or positions.
What it does
How often Wallbot compares the margin Binance reserves with its plan while it has orders or positions (one account request, weight 5).
Example
At 60 a re-margined order is noticed within about a minute.
When to change it
Lower it for faster alerts; raise it to save requests.
Higher, lower, on or off
Lower: faster alerts, more requests.
Risk notes
Low.
Never change leverage under Wallbot's own orders
leverage_hold_while_resting
- Default
- On
- Range
- On or off
- Type
- On/off
- Live confirmation
- No. Changes apply in every mode without the typed confirmation.
In the dashboard: While Wallbot has a resting entry or an open position on a coin, its leverage is never changed (Binance re-margins the resting order or position at the new leverage, which also shows up as 'foreign' margin). A re-plan sets the new leverage only after the old entry's cancel is confirmed; other evaluations that would need a different leverage are skipped with the reason.
What it does
While Wallbot has a resting entry, an open position or a closing trade on a coin, it never changes that coin's leverage. Binance re-margins resting orders and positions at a new leverage, which also shows up as foreign margin. A re-plan sets the new leverage only after the old entry's cancel is confirmed; other evaluations that need a different leverage are skipped with a logged reason.
Example
A BTCUSDT long rests at 50x. A closer wall would need 40x. On: the new leverage is set only after Binance confirms the old 50x entry is cancelled. Off: the coin is switched to 40x at once, and Binance re-margins the resting 50x order at 40x, so it suddenly needs 25% more margin.
When to change it
Leave it on for testnet and live. It does nothing in the paper shadow.
Higher, lower, on or off
On: the leverage of an order or position never changes under it. Off: the bot may change leverage while its own order or position is on that coin, changing its margin and liquidation price after the fact.
Risk notes
High if off: an open position's margin and liquidation distance can change without the stop being re-planned.
Foreign margin banner shows the sizing base
foreign_banner_sizing_base
- Default
- On
- Range
- On or off
- Type
- On/off
- Live confirmation
- No. Changes apply in every mode without the typed confirmation.
In the dashboard: The foreign-margin banner states the actual sizing base (available + Wallbot's own pending entries, then the cap) instead of only the available balance.
What it does
Chooses the wording of the foreign-margin banner. On, it states the real amount new entries are sized from: available balance plus Wallbot's own pending entries, then the cap if one is set. Off, it only mentions the available balance.
Example
20 USDT available and 6 USDT in Wallbot's own pending entries. On: "new entries are sized from 26.00 USDT (available 20.00 + Wallbot's own pending entries 6.00)". Off: "new entries are sized from the 20.00 USDT still available".
When to change it
Leave it on; the older wording understated the sizing base.
Higher, lower, on or off
On: the banner shows the actual sizing base and cap. Off: the shorter, less accurate wording.
Risk notes
Low: banner text only, sizing itself is unchanged.
Check every close against Binance
validate_close_with_binance
- Default
- On
- Range
- On or off
- Type
- On/off
- Live confirmation
- No. Changes apply in every mode without the typed confirmation.
In the dashboard: Live and testnet: after each close, Binance's fills, commissions, funding and average exit price for the trade are read (read-only, retried while Binance's history is not ready) and compared. A match marks the trade verified; a difference makes Binance's values the record (Wallbot's kept for reference), corrects the daily totals and loss caps, and sends an alert naming the difference. Never blocks trading.
What it does
After each live or testnet close, Wallbot reads that trade's fills, commissions, funding and average exit price from Binance and compares them with its own record. Match (within 0.0001 USDT, half a tick for the price): the trade is marked verified. Difference: Binance's values become the record, Wallbot's are kept for reference, the daily totals and loss caps are corrected, and an alert names the difference.
Example
A close recorded as PnL +2.1899, fees 0.0451, funding 0: Binance shows funding -0.0056, so the record becomes PnL +2.1843 with the note "corrected to Binance's values (Wallbot had PnL +2.1899 ...)" and the alert "funding +0.0000 -> -0.0056". If Binance's history is not ready, it retries after 3, 10, 30, 60 and 120 s.
When to change it
Leave it on in live and testnet. Turn it off only if the extra read-only requests after each close are unwanted.
Higher, lower, on or off
On: every close is checked and marked verified or corrected. Off: Wallbot's own values stay the record.
Risk notes
None for trading: it runs in the background after the close, only reads, and never blocks entries or exits.
Pause entries while the key or connection is unstable
key_unstable_guard
- Default
- On
- Range
- On or off
- Type
- On/off
- Live confirmation
- No. Changes apply in every mode without the typed confirmation.
In the dashboard: Live and testnet: after any -2015 (API key rejected, e.g. the PC's public IP changed) or a burst of -1021 clock rejections, new entries are paused until signed requests have been clean for 'Key stable for', and all resting entries are cancelled at the first request that gets through. Stops are never cancelled. While it is engaged and a position is open, its stop on Binance is checked every 15 s with high-priority alerts until it is confirmed. One notification when it engages and one when it clears (with the IPs Binance reported).
What it does
Protects live trading while Binance rejects the API key (-2015, typically because the PC's public IP changed to one that is not on the key's allow-list) or the connection is so slow that requests arrive too late (a burst of -1021). New entries pause, resting entries are cancelled at the first request that gets through, and entries resume only after signed requests have been clean for key_stable_minutes. Stops are never cancelled.
Example
At 19:32 the IP changes to 203.0.113.45 and Binance rejects the key: entries pause and you get "ENTRIES PAUSED: API KEY UNSTABLE (IP 203.0.113.45)". At 19:36 a request succeeds: the 4 resting entries are cancelled. From 19:36 to 19:46 every signed request succeeds: "ENTRIES RESUMED: API KEY STABLE".
When to change it
Leave it on. Turn it off only on a connection with a fixed public IP where -2015 cannot happen by accident.
Higher, lower, on or off
On: no new entries and no resting entries while the key or connection is unreliable, plus 15 s stop checks for open positions. Off: entries continue and an entry that fills while Binance rejects the key may sit without a stop until the key works again.
Risk notes
Off is risky on a connection whose public IP changes: an entry can fill when no stop or cancel can be sent.
Key stable for
key_stable_minutes
- Default
- 10 min
- Range
- 1 to 240 min
- Type
- Number
- Unit
- min
- Live confirmation
- No. Changes apply in every mode without the typed confirmation.
In the dashboard: How long signed requests must succeed without a -2015 or -1021 burst before the key guard lets new entries go again.
What it does
How long signed requests must succeed, with no -2015 and no -1021 burst, before the key guard allows new entries again.
Example
Default 10: the last rejection was at 19:35 and every request since has worked, so entries resume at 19:45. A new rejection at 19:40 would restart the wait until 19:50.
When to change it
Longer if your connection flips back and forth for a while; shorter if outages are brief and clear-cut.
Higher, lower, on or off
Higher: entries wait longer after a problem. Lower: entries resume sooner, with more risk of a new rejection right after.
Risk notes
Low. Very short values can let entries resume while the connection is still flipping between IPs.
Clock rejections that engage the key guard
key_unstable_1021_burst
- Default
- 3
- Range
- 1 to 100
- Type
- Whole number
- Live confirmation
- No. Changes apply in every mode without the typed confirmation.
In the dashboard: This many -1021 clock rejections (timestamp outside recvWindow) within a minute engage the key guard.
What it does
How many -1021 clock rejections within a minute count as an unstable connection and engage the key guard. A single -1021 is fixed by re-syncing the clock and retrying; a burst means requests are being delayed by seconds.
Example
Default 3: at 19:04 three requests in 40 s arrive outside the window (clock offset jumping between -0.5 and -6 s), so the guard engages.
When to change it
Raise it if occasional -1021 bursts on a slow connection pause entries too often (also consider a larger recv_window_ms).
Higher, lower, on or off
Higher: only heavier bursts engage the guard. Lower: the guard engages at the first signs of delay.
Risk notes
Low.
Alert on unprotected positions
unprotected_alert
- Default
- On
- Range
- On or off
- Type
- On/off
- Live confirmation
- No. Changes apply in every mode without the typed confirmation.
In the dashboard: Testnet and live: every reconciliation pass (every 60 s and after errors) checks that each bot position has a confirmed stop on Binance; if not, a high-priority notification (at most every 10 minutes per position) and a dashboard warning.
What it does
On testnet and live, every reconciliation pass checks that each bot position has a confirmed stop on Binance. If not, you get a high-priority notification (at most every 10 minutes per position) and a dashboard warning "UNPROTECTED POSITION".
Example
A HYPEUSDT long exists on Binance, but its stop id is not among Binance's open stop orders. Within one pass (60 seconds by default) the dashboard shows the warning and an alert is sent. If it is still unprotected 10 minutes later, you are alerted again.
When to change it
Leave it on. It needs periodic_reconcile on.
Higher, lower, on or off
On: positions without a working stop are reported quickly. Off: no such check, you only find out by looking at the exchange.
Risk notes
High if off: an unprotected position can go unnoticed. Note it depends on your notification settings to reach you.
Delisting guard
delist_guard I ACCEPT in live
- Default
- On
- Range
- On or off
- Type
- On/off
- Live confirmation
- Yes: lowering it in live mode asks you to type I ACCEPT.
In the dashboard: When Binance announces a delisting or the removal of a coin's USD-M perpetual, no new Wallbot entries on that coin (all its contracts), its pending entry orders are cancelled and you get a high-priority alert; open positions are still managed. Read from the shared file both instances use.
What it does
Watches Binance's official announcements for delistings and USD-M contract removals. For an affected coin (all its contracts, USDT and USDC): no new Wallbot entries, its pending entry orders are cancelled, and one high-priority alert per announcement lists your open Wallbot and manual positions on that coin. Open positions keep being managed as before; nothing is closed. The block stays until you clear it in the Events panel (false alarm) or the coin is gone.
Example
Binance posts 'Binance Futures Will Delist USDⓈ-M XYZUSDT Perpetual Contract' at 14:02 UTC: within 5 seconds both instances stop entering XYZUSDT and XYZUSDC, a resting XYZUSDT entry is cancelled, and you get 'DELISTING XYZ: new entries blocked - POSITIONS OPEN' if you hold XYZ.
When to change it
Leave it on.
Higher, lower, on or off
On: no new trades on coins that are about to be delisted. Off: announcements are still shown, but nothing is blocked.
Risk notes
Low. A false match only blocks new entries on one coin until you clear it.
Delisting guard: listen here
delist_guard_listen I ACCEPT in live
- Default
auto- Choices
auto,on,off- Type
- Choice
- Live confirmation
- Yes: any change in live mode asks you to type I ACCEPT.
In the dashboard: Which instance connects to Binance's announcement stream (signed with its saved Binance Live key; no order or account request). auto = the Trading instance only. The other instance reads the shared file.
What it does
Which instance keeps the connection to Binance's announcement WebSocket (topic com_announcement_en). Binance requires the connection to be signed with an API key; this instance's saved Binance Live key is used for the signature only (no order or account request). The listener writes what it finds to a shared file that both instances read.
Example
auto: the Trading instance (8788) listens; the Research instance (8787) only reads the shared file.
When to change it
Leave it on auto. on makes this instance listen too; off never listens here.
Higher, lower, on or off
auto / on / off as described; with no instance listening, nothing new is detected.
Risk notes
Low. The key is only used to sign the connection.