Wallbot

Settings reference / Entries

Entries settings

How and where entries are placed: entry model, sizing and leverage, re-plans, side switches, the support/resistance level filter and reward/risk. 70 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

SettingInternal nameDefault
Target net ROE for the room checktarget_net_roe10 %
Entry modelentry_modelwall_hug
Stop placement (wall hug)stop_modewall_pct
Entry anchor (wall hug)entry_anchorstack
Wall stack spanstack_max_span_pct1.5 %
Stack entry modeentry_stack_modeOff
Stack entry: minimum wallsstack_min_walls2
Stack entry: positionentry_stack_positionfront
Stack entry: front-wall guardstack_front_guardOn
Front-wall guard: minimum refillstack_guard_refill_min0.2
Front-wall guard: windowstack_guard_window_s20 s
Front-wall guard: minimum tradedstack_guard_min_traded_usdt3000 USDT
Front-wall guard: modestack_guard_modewall
Stack zone: refill windowstack_refill_window_s90 s
Stack zone: shrink for a hitstack_zone_shrink_pct50 %
Stack zone: hold after the fill while it refillsstack_hold_on_refillOff
Front-wall guard: pause after a cancelstack_guard_cooldown_s300 s
Skip entries against the order-book imbalanceentry_imbalance_filterOff
Minimum book imbalance at entrymin_entry_book_imbalance-0.1
Try deeper walls when reward/risk failsrr_try_deeper_wallOff
Paper shadow: skip entries against the book imbalanceshadow_entry_imbalance_filterOff
Re-plan on a closer wallreplan_on_closer_wallOn
Re-plan after the front wall is pulledreplan_after_front_pullOn
Re-plan cooldownreplan_cooldown_s60 s
Nearest-side prioritynearest_side_priorityOff
Side switch: closer by at leastside_switch_closer_pct30 %
Side switch: cooldownside_switch_cooldown_s60 s
Side switch: not when about to fillside_switch_min_dist_pct0.1 %
Re-plan when the stack loses a wallreplan_on_stack_lossOn
Minimum reward/riskmin_reward_risk1
Allow long and short on one coinallow_both_sidesOff
S/R rule for wall stackssr_stack_ruleany
Wall hug leverage caphug_max_leverage0 x
Entry ticks in front of wallentry_ticks1 ticks
Leverage modeleverage_modefixed
Leverageleverage50 x
Leverage capleverage_cap50 x
Margin per entrymargin_pct2 %
Entry order timeoutpending_timeout_s300 s
Cancel entries far from priceentry_cancel_far_atr_mult0 x ATR
Entry maximum ageentry_max_age_s0 s
Require a higher-timeframe levelsr_filterOn
24h high/low as a levellevel_24h_modeoff
Level timeframesr_timeframe4h
Level lookbacksr_lookback_days30 days
Pivot strengthsr_pivot_strength2 candles
Level tolerancesr_tolerance_pct0.3 %
Level tolerance modesr_tolerance_modefixed_pct
Level tolerance ATR multiplesr_tol_atr_mult0.1
Level tolerance minimumsr_tol_min_pct0.05 %
Level tolerance maximumsr_tol_max_pct0.5 %
Wall retry cooldownwall_retry_cooldown_s30 s
Closer-wall re-plan intervalreplan_min_interval_s30 s
Deeper walls tried at mostrr_deeper_max_walls3
Watch: try deeper wallsshadow_rr_try_deeper_wallOff
Watch: 24h high/low as a levelshadow_level_24h_modeoff
Opposite entry after a take profittp_opposite_priorityOn
Opposite-entry priority windowtp_opposite_priority_s90 s
Counter wall minimum remaining sizetp_flip_min_remaining_pct50 %
Failed counter wall must re-confirmtp_flip_reconfirmOn
Sizing basesizing_baseavailable_plus_own_pending
Require free margin to openrequire_free_marginOn
Free margin bufferfree_margin_buffer_pct5 % of the margin
Re-check closer walls after the re-plan limitreplan_recheck_after_limitOn
Core: sizingcore_sizing_modeinherit
Core: sizing valuecore_sizing_value0 % or USDT
Movers: sizingmovers_sizing_modeinherit
Movers: sizing valuemovers_sizing_value0 % or USDT
My coins: sizingpinned_sizing_modeinherit
My coins: sizing valuepinned_sizing_value0 % or USDT

All settings

Target net ROE for the room check

target_net_roe

Default
10 %
Range
0.1 to 1000 %
Type
Number
Unit
%
Live confirmation
No. Changes apply in every mode without the typed confirmation.

In the dashboard: Analysis only: required_move_pct is the price move giving this net ROE after fees and slippage at the planner's leverage.

What it does

Analysis value. The wall-flow measurements include a "required move": the price move that would earn this net ROE (percent of margin) after maker entry, taker exit and slippage, at the leverage the planner would use. It is also what required_move_pct and room_ok mean in a flow_filter.

Example

Target 10% at 20x, maker 0.02%, taker 0.05%, slippage 5 bps: required move = 10% / 20 + 0.02% + 0.05% + 0.05% = 0.62% of price.

When to change it

Change it if you study a different profit goal per trade in the flow log, or if your flow_filter uses required_move_pct or room_ok.

Higher, lower, on or off

Higher: a bigger required move, so fewer walls show room_ok. Lower: a smaller required move, so more walls show room_ok.

Risk notes

Low with an empty flow_filter (it only changes logged numbers). If your flow_filter uses these fields, it changes which entries pass.

Entry model

entry_model

Default
wall_hug
Choices
wall_hug, loss_budget
Type
Choice
Live confirmation
No. Changes apply in every mode without the typed confirmation.

In the dashboard: Wall hug: entry a few ticks in front of the wall, stop a few ticks behind it, at the highest leverage the exchange allows (leverage settings below are not used). Loss budget: the older model that places the entry so a stop-out costs the loss target, at the leverage below.

What it does

Chooses how entries, stops and leverage are planned. wall_hug puts the entry a few ticks in front of the wall and the stop behind it, then picks the highest leverage that passes every safety check. loss_budget is the older model: it places the entry so a stop-out costs the loss target, at the fixed leverage.

Example

With wall_hug on BTC (tick 0.1) and a bid wall whose near edge is 60000: entry 60000.1 (entry_ticks 1). The leverage search starts at the exchange maximum (or hug_max_leverage) and steps down until the liquidation, fee and size checks pass.

When to change it

Keep wall_hug unless you are comparing against the older behaviour in a backtest or paper run.

Higher, lower, on or off

wall_hug: uses stop_mode, entry_anchor, the liquidation buffers, max_fee_pct_of_margin, take profit and the re-plan features; leverage is ignored. loss_budget: uses leverage and the loss target; take profit at the counter wall, re-plans and the stack features do not run.

Risk notes

High impact: it changes leverage, stop distance and which other settings apply. Test a change in paper mode first.

Stop placement (wall hug)

stop_mode

Default
wall_pct
Choices
wall_pct, near_liquidation, wall_ticks
Type
Choice
Live confirmation
No. Changes apply in every mode without the typed confirmation.

In the dashboard: Wall %: the stop sits a set percentage behind the wall's far edge and the bot uses the highest leverage whose exact liquidation stays safely behind that stop. Near liquidation: the stop sits just before the liquidation price, so a stop-out loses most of the margin. Wall ticks: the stop sits a few ticks behind the wall.

What it does

Wall hug only. Decides where the stop goes. The leverage picker then finds the highest leverage whose exact liquidation price is still safely behind that stop.

Example

Long, wall far edge 59800, wall_pct with stop_beyond_wall_pct 0.5: stop 59800 x 0.995 = 59501.0. With wall_ticks and stop_ticks 3 (tick 0.1): stop 59799.7. With near_liquidation: the stop sits just in front of liquidation, minus the buffer from liq_buffer_pct_of_margin.

When to change it

Change it if you want the stop further from the wall (more room, lower leverage) or tighter to it.

Higher, lower, on or off

wall_pct: stop a set percentage behind the wall's far edge (or behind the farthest wall of the stack). near_liquidation: stop just before liquidation, so a stop-out loses most of the margin; it must still be behind the wall. wall_ticks: stop stop_ticks behind the far edge, and the loss at the stop must stay within max_loss_pct.

Risk notes

near_liquidation means a stop-out costs most of the margin and leaves little room for error. Every mode keeps the slipped stop fill at least the liquidation buffer away from liquidation.

Entry anchor (wall hug)

entry_anchor

Default
stack
Choices
stack, single_wall
Type
Choice
Live confirmation
No. Changes apply in every mode without the typed confirmation.

In the dashboard: Stack: with several confirmed walls on one side, enter in front of the nearest and put the stop behind the farthest one within the stack span (the leverage follows, so liquidation is behind every wall). Single wall: enter and stop around one wall only (the older behaviour).

What it does

Wall hug only. With stack, if several confirmed walls sit close together on one side, the bot enters in front of the nearest and puts the stop behind the farthest one inside stack_max_span_pct. With single_wall, it plans around one wall only.

Example

Long: walls at 60000 (near edge) and 59300 (far edge), span 1.5%. 59300 is 1.17% from 60000, so it joins the stack. Entry 60000.1, stop 0.5% behind 59300 = 59003.5 (with wall_pct).

When to change it

Use single_wall if you prefer tighter stops and accept that breaking the first wall usually stops you out.

Higher, lower, on or off

stack: wider stop behind every wall in the stack, leverage drops to keep liquidation behind all of them; enables stop tightening as stack walls go. single_wall: stop around one wall, tighter, higher leverage possible.

Risk notes

Medium: stack means a larger price distance to the stop; single_wall means one wall break ends the trade.

Wall stack span

stack_max_span_pct

Default
1.5 %
Range
0.05 to 10 %
Type
Number
Unit
%
Live confirmation
No. Changes apply in every mode without the typed confirmation.

In the dashboard: Stack: a confirmed wall joins the stack when its far edge is within this distance of the nearest wall's near edge.

What it does

With entry_anchor = stack: a confirmed wall joins the stack if its far edge is within this distance of the nearest wall's near edge.

Example

Nearest wall near edge 60000, span 1.5%. A wall with far edge 59200 (1.33% away) joins. A wall with far edge 59000 (1.67% away) does not.

When to change it

Raise it to include walls further back (wider stops). Lower it to keep stacks tight.

Higher, lower, on or off

Higher: more walls in the stack, the stop goes further back, lower leverage. Lower: smaller stacks, behaves more like single_wall.

Risk notes

Medium: a large span can put the stop far from entry, so a stop-out costs more of the margin per trade.

Stack entry mode

entry_stack_mode I ACCEPT in live used only with entry_model wall_hug

Default
Off
Range
On or off
Type
On/off
Live confirmation
Yes: any change in live mode asks you to type I ACCEPT.

In the dashboard: Wall hug only. On: enter only on a stack of at least 'Stack entry: minimum walls' confirmed walls within the stack span, at the position below, with the stop behind the farthest wall (the stack is used whatever the entry anchor says). Off: today's entries.

What it does

Wall hug only. On: the bot enters only when at least stack_min_walls confirmed walls sit within stack_max_span_pct on one side, places the entry in front of the wall chosen by entry_stack_position, and puts the stop behind the farthest wall of the stack. It uses the stack even if entry_anchor is single_wall. Off: entries work exactly as today.

Example

Long, walls at 99.50, 98.90 and 98.40 (span 1.5%), position biggest, and 98.90 is the largest: the entry rests 1 tick (entry_ticks) above the biggest orders of the 98.90 wall; the stop is behind 98.40.

When to change it

For a paper test of deeper entries in strong stacks. Keep it off on the live instance until a test supports it.

Higher, lower, on or off

Fewer entries (single walls are skipped). A deeper position gives a better price and a closer stop but fills less often: price has to get through the walls in front first.

Risk notes

Medium: fewer fills, and the fills that happen are the ones where price went through walls in front of the entry.

Stack entry: minimum walls

stack_min_walls I ACCEPT in live used only with entry_model wall_hug

Default
2
Range
1 to 10
Type
Whole number
Live confirmation
Yes: lowering it in live mode asks you to type I ACCEPT.

In the dashboard: Stack entry mode: the confirmed walls needed within the stack span.

What it does

Stack entry mode: how many confirmed walls must sit within stack_max_span_pct (the nearest one included).

Example

2: a nearest wall plus at least one more within the span. 3: two more.

When to change it

Raise it to trade only thicker stacks.

Higher, lower, on or off

Higher: fewer, stronger stacks. 1: any wall qualifies (like today, but with the position and the guard).

Risk notes

Low.

Stack entry: position

entry_stack_position I ACCEPT in live used only with entry_model wall_hug

Default
front
Choices
front, biggest, middle, second_to_last
Type
Choice
Live confirmation
Yes: any change in live mode asks you to type I ACCEPT.

In the dashboard: Stack entry mode: the wall the entry is placed in front of (entry ticks in front of its biggest orders). Front = the nearest wall (today). Biggest = the largest wall. Middle = wall n/2 counted from the front (2 walls: the back one). Second to last = the wall before the farthest (2 walls: the front one).

What it does

Stack entry mode: which wall of the stack the entry is placed in front of, entry_ticks ticks in front of that wall's biggest orders (the finest price step). front = the nearest wall (today). biggest = the wall with the largest size (ties: the nearer one). middle = wall n/2 counted from the front (2 walls: the back wall; 3: the second; 4: the third). second_to_last = the wall before the farthest one (2 walls: the front wall).

Example

Short, ask walls at 100.50, 100.90, 101.30, 101.80: front 100.50, middle 101.30, second_to_last 101.30, biggest whichever is largest. The stop is always behind 101.80.

When to change it

Choose the position you want to test; front keeps today's entry price.

Higher, lower, on or off

Deeper positions: a better entry price and less distance to the stop (higher leverage possible), fewer fills.

Risk notes

Medium: a deeper entry only fills after walls in front of it are taken out or pulled.

Stack entry: front-wall guard

stack_front_guard I ACCEPT in live used only with entry_model wall_hug

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: Stack entry mode: cancel a pending entry when a wall in front of it is pulled, or is eaten without being replenished (refill below the minimum).

What it does

Stack entry mode: while the entry is pending, cancel it when a wall in front of it is pulled or faded, or is eaten without being replenished (refill below stack_guard_refill_min, checked during stack_guard_window_s after the wall's first touch and when the wall ends). After a cancel, no new stack entry on that coin and side for stack_guard_cooldown_s.

Example

Entry in front of the 98.90 wall; the 99.50 wall in front is hit, 8,000 USDT traded at it in 6 s and it shrank by almost all of that (refill 5%): the entry is cancelled.

When to change it

On by default. Turn it off to test deeper entries without the guard.

Higher, lower, on or off

Fewer fills: only entries whose walls in front were pulled never, and eaten only while being replenished, can fill. A fast sweep through a front wall within the window may still fill before the check.

Risk notes

Low: it only cancels pending entries; open positions are not touched.

Front-wall guard: minimum refill

stack_guard_refill_min I ACCEPT in live used only with entry_model wall_hug

Default
0.2
Range
0 to 1
Type
Number
Live confirmation
Yes: lowering it in live mode asks you to type I ACCEPT.

In the dashboard: Front-wall guard: refill ratio since the wall's first touch ((traded - shrink) / traded) below this = not replenished.

What it does

Front-wall guard: a front wall counts as replenished when its refill ratio since the first touch, (traded at the wall - how much it shrank) / traded, is at least this.

Example

0.2: 10,000 traded at the wall and it shrank by 7,000 = refill 0.3, replenished. Shrank by 9,500 = 0.05, not replenished.

When to change it

Raise it to demand stronger refilling (more cancels).

Higher, lower, on or off

Higher: more cancels, fewer fills.

Risk notes

Low.

Front-wall guard: window

stack_guard_window_s I ACCEPT in live used only with entry_model wall_hug

Default
20 s
Range
1 to 600 s
Type
Number
Unit
s
Live confirmation
Yes: lowering it in live mode asks you to type I ACCEPT.

In the dashboard: Front-wall guard: while the entry is pending, a front wall is checked for being eaten during this long after its first touch (a wall that ends is always checked).

What it does

Front-wall guard: how long after a front wall's first touch the guard watches it being eaten. A front wall that ends (pulled, faded, absorbed, broken) is checked whenever it happens.

Example

20 s: a wall touched at 12:00:00 is watched until 12:00:20.

When to change it

Longer windows catch slow absorption.

Higher, lower, on or off

Longer: more cancels.

Risk notes

Low.

Front-wall guard: minimum traded

stack_guard_min_traded_usdt I ACCEPT in live used only with entry_model wall_hug

Default
3000 USDT
Range
0 to 1e+07 USDT
Type
Number
Unit
USDT
Live confirmation
Yes: raising it in live mode asks you to type I ACCEPT.

In the dashboard: Front-wall guard: the window check needs at least this much traded at the front wall.

What it does

Front-wall guard: the window check needs at least this much traded at the front wall before a low refill ratio counts (a few small trades say little).

Example

3000: 1,200 USDT traded with a refill of 0 is not enough to cancel.

When to change it

Raise it on coins with large walls.

Higher, lower, on or off

Higher: fewer window cancels.

Risk notes

Low.

Front-wall guard: mode

stack_guard_mode I ACCEPT in live used only with entry_model wall_hug

Default
wall
Choices
wall, zone, off
Type
Choice
Live confirmation
Yes: any change in live mode asks you to type I ACCEPT.

In the dashboard: Stack entry mode. Wall: watch each wall in front of the entry on its own (as before). Zone: watch the whole stack as one zone; a hit followed by refill within the refill window is a defence and never cancels; cancel only if the zone shrinks by more than the zone shrink and does not refill within the window. Off: no guard.

What it does

Stack entry mode, with stack_front_guard on. wall: each wall in front of the pending entry is watched on its own (pulled or eaten without refill cancels; r47). zone: the whole stack is watched as one zone (all its walls combined, from the nearest wall to the farthest): a hit that refills within stack_refill_window_s is a defence and never cancels, also after a fast wick through the zone; the entry is cancelled only if the zone shrinks by more than stack_zone_shrink_pct and does not refill within the window. off: no guard.

Example

Zone 2.0M USDT at the entry, shrink 50%: a sweep takes it to 0.6M, bids are back to 1.5M after 40 s: a defence, the entry stays. Still at 0.6M after 90 s: cancelled.

When to change it

zone when single walls in a stack are often eaten and replaced; wall for the stricter r47 guard.

Higher, lower, on or off

zone cancels less often than wall; off never cancels.

Risk notes

Low: it only cancels pending entries.

Stack zone: refill window

stack_refill_window_s I ACCEPT in live used only with entry_model wall_hug

Default
90 s
Range
5 to 1800 s
Type
Number
Unit
s
Live confirmation
Yes: any change in live mode asks you to type I ACCEPT.

In the dashboard: Zone guard and zone hold: how long a hit zone has to refill (orders coming back at or near the same prices).

What it does

Zone guard, zone hold and the zone log: how long a hit zone has to refill (orders coming back at or near the same prices) before it counts as not refilled.

Example

90: hit at 12:00:00, judged at 12:01:30.

When to change it

Longer for slow books.

Higher, lower, on or off

Longer: fewer zone cancels / exits, later reactions.

Risk notes

Medium with the zone hold: a longer window keeps an unprotected position open longer.

Stack zone: shrink for a hit

stack_zone_shrink_pct I ACCEPT in live used only with entry_model wall_hug

Default
50 %
Range
5 to 95 %
Type
Number
Unit
%
Live confirmation
Yes: raising it in live mode asks you to type I ACCEPT.

In the dashboard: Zone guard and zone hold: the zone (all stack walls combined) is hit when its size falls by more than this from its size at the entry; refilled when it is back above that line.

What it does

A stack zone is hit when its size (all walls combined, notional on its side inside the stack's price range) falls by more than this from its size when the entry was placed; refilled when it is back above that line.

Example

50: a 2.0M zone is hit below 1.0M and refilled at 1.0M or more.

When to change it

Raise it to react only to deep hits.

Higher, lower, on or off

Higher: fewer hits.

Risk notes

Low.

Stack zone: hold after the fill while it refills

stack_hold_on_refill I ACCEPT in live used only with entry_model wall_hug

Default
Off
Range
On or off
Type
On/off
Live confirmation
Yes: switching it on in live mode asks you to type I ACCEPT.

In the dashboard: Open stack trades: when the wall under the position is pulled or eaten, wait the refill window. If the stack zone refills (or never shrinks past the line), the position counts as protected (no wall-gone exit and no unprotected-breakeven move); if it does not refill, act as without this setting.

What it does

Open stack trades (stack entry mode or a multi-wall stack): when the wall under the position is pulled, faded, absorbed or broken, the bot waits stack_refill_window_s. If the stack zone refills, or never shrank past stack_zone_shrink_pct, the position counts as still protected: no wall-gone exit and no unprotected-breakeven move. If the zone does not refill in the window, the bot acts exactly as without this setting. Every stack fill's zone hits and refills after the fill are logged with how the trade ended, also with this off.

Example

Long on a 3-wall stack; the front wall is eaten, the zone drops to 40%, bids return to 70% within 30 s: the position is kept with its stop. Without the refill within 90 s: the wall-gone exit runs.

When to change it

Test on paper first (see the stack-entry paper test plan).

Higher, lower, on or off

Fewer early exits on stacks that defend themselves; the stop always stays in place.

Risk notes

Medium: a position can stay open up to the window without its wall; the stop still protects it.

Front-wall guard: pause after a cancel

stack_guard_cooldown_s I ACCEPT in live used only with entry_model wall_hug

Default
300 s
Range
0 to 7200 s
Type
Number
Unit
s
Live confirmation
Yes: lowering it in live mode asks you to type I ACCEPT.

In the dashboard: After the guard cancels an entry, no new stack entry on that coin and side for this long.

What it does

After the front-wall guard cancels an entry, no new stack entry on that coin and side for this long (otherwise the next wall of the stack could be re-entered at once).

Example

300: a guard cancel at 12:00 blocks stack entries on that coin and side until 12:05.

When to change it

Shorter to re-enter sooner after a cancel.

Higher, lower, on or off

Longer: fewer re-entries after a guard cancel.

Risk notes

Low.

Skip entries against the order-book imbalance

entry_imbalance_filter Paper shadow: shadow_entry_imbalance_filter

Default
Off
Range
On or off
Type
On/off
Live confirmation
No. Changes apply in every mode without the typed confirmation.

In the dashboard: Skip an entry (also a re-place or re-plan) when the order-book imbalance within 0.5% of the price, measured at placement, leans against the trade by more than min_entry_book_imbalance. Imbalance = (bid - ask) / (bid + ask) notional within 0.5% of the mid, signed in the trade's favour (+ = the book leans our way). Off by default; shadow_entry_imbalance_filter runs it in the paper shadow only.

What it does

Skips an entry, including a re-place or re-plan, when the order book within 0.5% of the price, measured at placement, leans against the trade by more than min_entry_book_imbalance. Imbalance = (bid notional - ask notional) / (bid + ask) within 0.5% of the mid, signed in the trade's favour: +0.2 means the book leans toward the trade, -0.2 against it. The log reads "Skipped wall: order-book imbalance within 0.5% is -0.18 against this long (minimum -0.10, entry_imbalance_filter)". Off by default; shadow_entry_imbalance_filter runs it in the paper shadow only.

Example

Long at a support wall: within 0.5% there are 1.2 M USDT of bids and 1.8 M of asks, imbalance (1.2 - 1.8) / 3.0 = -0.20. With the default -0.1 the entry is skipped; at -0.05 against it, it would be placed.

When to change it

After the paper comparison: on 338 live fills (09-29 to 10-18) skipping below -0.1 removed 31% of the fills, 15 of the 55 "wall vanished before fill confirmed" exits, and improved net PnL in both halves of the period.

Higher, lower, on or off

On: fewer entries, mostly those where the nearby book is against the trade. Off: unchanged.

Risk notes

Low. It only skips entries; it can skip some that would have won.

Minimum book imbalance at entry

min_entry_book_imbalance

Default
-0.1
Range
-1 to 1
Type
Number
Live confirmation
No. Changes apply in every mode without the typed confirmation.

In the dashboard: entry_imbalance_filter: the entry is skipped when the imbalance in the trade's favour is below this (-0.1 = the book leans against the trade by more than 0.1).

What it does

entry_imbalance_filter: the entry is skipped when the order-book imbalance within 0.5% of the price, in the trade's favour, is below this value. Negative values allow a book that leans somewhat against the trade.

Example

At -0.1 a long is skipped when the imbalance is -0.15 and placed when it is -0.05. For a short the sign is flipped: more asks than bids counts in its favour.

When to change it

Raise it toward 0 for a stricter filter (fewer entries); lower it toward -1 to skip only strongly opposed books.

Higher, lower, on or off

Higher: more entries skipped. Lower: fewer.

Risk notes

Low.

Try deeper walls when reward/risk fails

rr_try_deeper_wall I ACCEPT in live Watch (log only): shadow_rr_try_deeper_wall

Default
Off
Range
On or off
Type
On/off
Live confirmation
Yes: switching it on in live mode asks you to type I ACCEPT.

In the dashboard: When the nearest wall fails only the minimum reward/risk, try the next confirmed walls on the same side (nearest first, within the wall range, at most rr_deeper_max_walls) and place on the first one that passes every entry check; the take profit stays before the nearest counter wall. Single-wall anchoring only. Off by default; shadow_rr_try_deeper_wall logs what it would do.

What it does

When the nearest confirmed wall fails only the minimum reward/risk, Wallbot tries the next confirmed walls on the same side, nearest first, within the wall range (at most rr_deeper_max_walls), and places on the first one that passes every entry check (level filter, safety, sizing, liquidation, reward/risk, imbalance). The take profit stays before the nearest counter wall. Works with single-wall anchoring (with stacks the deeper walls within the span are already used). The log reads "Reward/risk 0.92 too low at the nearest wall ...: using the deeper wall ... (reward/risk 1.84, rr_try_deeper_wall)".

Example

Long: nearest support 81.47-81.51, take profit 81.50 before resistance, stop 81.79 below gives reward/risk 0.92 < 1. A deeper support at 81.10-81.15 (0.5% away) gives reward/risk 1.8 and passes all checks: the entry goes there.

When to change it

Only after the watch data shows deeper walls end better than the skipped trades. On 8788 (10-17 to 10-22) 92% of such deeper entries would not have filled within 5 minutes, and of the rest 6 reached take profit and 11 the stop.

Higher, lower, on or off

On: more entries, farther from the price (fewer fills, larger reward per fill). Off: unchanged.

Risk notes

Medium: extra entries the strategy did not take before; each still passes every check.

Paper shadow: skip entries against the book imbalance

shadow_entry_imbalance_filter

Default
Off
Range
On or off
Type
On/off
Live confirmation
No. Changes apply in every mode without the typed confirmation.

In the dashboard: Run entry_imbalance_filter in the paper shadow only (testnet/live instances): the shadow skips the live entries the filter would have skipped, so the two can be compared on the same signals. The live engine follows entry_imbalance_filter.

What it does

Runs entry_imbalance_filter in the paper shadow only (testnet and live instances): the shadow does not copy the live entries the filter would have skipped, so the shadow results show the effect on exactly the same signals. The live engine keeps following entry_imbalance_filter.

Example

Live off, shadow on: a live long is placed with the book at -0.20; the shadow logs "Skipped wall: order-book imbalance ... -0.20" and has no copy of that trade.

When to change it

Turn it on to measure the filter before using it live.

Higher, lower, on or off

Only the paper shadow changes.

Risk notes

None for live trading.

Re-plan on a closer wall

replan_on_closer_wall

Default
On
Range
On or off
Type
On/off
Live confirmation
No. Changes apply in every mode without the typed confirmation.

In the dashboard: Pending entry: when a new confirmed wall appears on the same side between price and our entry, cancel and re-plan on the rebuilt stack (new nearest wall), but only if the new plan passes every check; at most once per 30 s per coin and side.

What it does

Pending entry only. When a new confirmed wall appears on the same side between price and the entry, the bot cancels and re-plans on the rebuilt stack (the new nearest wall), but only if the new plan passes every check. Limited by replan_min_interval_s per coin and side.

Example

Pending long at 60000.1. A new confirmed bid wall appears at 60150. The bot re-plans: entry 60150.1, stop behind the farthest wall in the stack, leverage recalculated. If the new plan fails a check, the old entry stays.

When to change it

Turn off if re-plans cause too many cancel and replace orders.

Higher, lower, on or off

On: entries follow the nearest wall, so they sit closer to price and are more likely to fill. Off: the pending entry stays where it was placed.

Risk notes

Low: the new plan must pass the same checks. It adds order traffic. Wall hug only.

Re-plan after the front wall is pulled

replan_after_front_pull

Default
On
Range
On or off
Type
On/off
Live confirmation
No. Changes apply in every mode without the typed confirmation.

In the dashboard: Pending entry whose front wall is pulled or fades while other confirmed walls remain: after the cancel, wait replan_cooldown_s, then re-plan on the remaining walls. Off: the normal entry logic may place a new entry on the remaining walls right away.

What it does

Pending entry whose front wall is pulled or fades while other confirmed walls remain. After the cancel, the bot waits replan_cooldown_s and then re-plans on the remaining walls. New entries on that coin and side also wait for the cooldown.

Example

Pending long on the 60000 wall; walls at 59500 and 59300 remain. The 60000 wall is pulled: entry cancelled, "re-planning in 60 s", then a new plan on the 59500 wall if it passes.

When to change it

Turn off if you want the normal entry logic to place a new entry on the remaining walls right away.

Higher, lower, on or off

On: a pause after a pull before re-entering on that side. Off: no forced pause; the normal entry logic may place a new entry immediately.

Risk notes

Low. A pull is often a spoof sign, so the pause avoids jumping straight back in. Wall hug only.

Re-plan cooldown

replan_cooldown_s

Default
60 s
Range
0 to 3600 s
Type
Whole number
Unit
s
Live confirmation
No. Changes apply in every mode without the typed confirmation.

In the dashboard:

What it does

How long the bot waits after a pulled front wall before it re-plans on the remaining walls (see replan_after_front_pull). Entries on that coin and side are held back until then.

Example

60: wall pulled at 12:00:00, re-plan at 12:01:00. 0: re-plan on the next check.

When to change it

Raise it if pulls are often followed by more pulls on the same coin. Lower it to get back in sooner.

Higher, lower, on or off

Higher: longer pause, fewer re-entries right after spoofs, some missed chances. Lower: faster re-entry.

Risk notes

Low: it only delays entries.

Nearest-side priority

nearest_side_priority

Default
Off
Range
On or off
Type
On/off
Live confirmation
No. Changes apply in every mode without the typed confirmation.

In the dashboard: A coin has a pending entry on one side and a fully qualifying setup appears on the other side: if the other side's entry is at least side_switch_closer_pct closer to the price, cancel the pending entry (confirmed) and place the closer one. Never within side_switch_min_dist_pct of the price, at most one switch per coin per side_switch_cooldown_s, never a filled position.

What it does

When a coin has a pending (not yet filled) entry on one side and a setup on the OTHER side passes every normal check (4h level, reward/risk, fees, liquidation with the slippage buffer, free balance, correlation, max positions), the bot compares how far each entry is from the current price. If the other side's entry is at least side_switch_closer_pct closer, it cancels the pending entry and waits for the cancel to be confirmed, then sets the leverage and places the closer setup. If the new placement fails, the reason is logged and the old entry is not re-placed automatically (it is placed again only if it still qualifies on a later check). Safeguards: never when the pending entry is within side_switch_min_dist_pct of the price, at most one switch per coin per side_switch_cooldown_s, never a filled position. Same-side re-plans are unchanged (replan_on_closer_wall). Logged and notified.

Example

On, 30%: TAOUSDT at 300.00 has a pending short at 303.00 (1.00% away). A support wall qualifies with a long entry at 299.40 (0.20% away, 80% closer): the short is cancelled, then the long is placed. 'side switch: cancelled pending short at 303 (1.00% from the price, farther), placed long at 299.4 (0.20%, closer)'.

When to change it

Try it on the paper instance first; it trades more often near the price.

Higher, lower, on or off

On: a far entry no longer blocks a much closer one on the other side. Off: the first pending entry keeps the coin until it fills or is cancelled.

Risk notes

Medium: more cancels and re-placements, and the closer entry may be the weaker setup.

Side switch: closer by at least

side_switch_closer_pct

Default
30 %
Range
1 to 100 %
Type
Number
Unit
%
Live confirmation
No. Changes apply in every mode without the typed confirmation.

In the dashboard: How much closer to the price (relative) the other side's entry must be.

What it does

How much closer to the price the other side's entry must be for a side switch, relative to the pending entry's distance.

Example

At 30%: a pending entry 1.0% from the price is replaced only by one at most 0.7% away.

When to change it

Raise it to switch only for clearly closer setups.

Higher, lower, on or off

Higher: fewer switches. Lower: more.

Risk notes

Low.

Side switch: cooldown

side_switch_cooldown_s

Default
60 s
Range
0 to 3600 s
Type
Whole number
Unit
s
Live confirmation
No. Changes apply in every mode without the typed confirmation.

In the dashboard: At most one side switch per coin within this time.

What it does

At most one side switch per coin within this many seconds.

Example

At 60: after a switch on TAOUSDT at 12:00:00, the next switch on TAOUSDT can happen from 12:01:00.

When to change it

Raise it if a coin flips back and forth.

Higher, lower, on or off

Higher: calmer. Lower: reacts faster.

Risk notes

Low.

Side switch: not when about to fill

side_switch_min_dist_pct

Default
0.1 %
Range
0 to 5 %
Type
Number
Unit
%
Live confirmation
No. Changes apply in every mode without the typed confirmation.

In the dashboard: Never switch when the pending entry is within this % of the price.

What it does

A pending entry within this % of the current price is about to fill and is never cancelled for a side switch.

Example

At 0.1%: a pending short at 300.25 with the price at 300.00 (0.08% away) stays.

When to change it

Leave it.

Higher, lower, on or off

Higher: protects more entries close to filling.

Risk notes

Low.

Re-plan when the stack loses a wall

replan_on_stack_loss

Default
On
Range
On or off
Type
On/off
Live confirmation
No. Changes apply in every mode without the typed confirmation.

In the dashboard: Pending entry on a multi-wall stack: when a wall of the stack fades, is pulled, absorbed or broken before the fill, cancel (confirmed) and re-plan at once from the remaining walls with the normal planner (entry in front of the nearest, stop behind the farthest, the highest leverage with liquidation protected behind that stop and every entry check). If the new plan fails, the entry is cancelled. A pulled or faded FRONT wall keeps the replan_cooldown_s wait (replan_after_front_pull).

What it does

A resting entry planned on a stack of several walls is re-planned as soon as one of those walls disappears before the fill (fades, is pulled, absorbed or broken). The bot runs the normal planner on the walls that remain: the entry goes in front of the nearest remaining wall, the stop behind the farthest remaining wall, at the highest leverage whose liquidation stays protected behind that stop (with the slippage buffer, the fee cap and every other entry check). It cancels the old entry and waits for the cancel to be confirmed, then sets the new leverage, then places the new order. If the new plan is identical (a middle wall went), the order stays. If the new plan fails a check, the entry is cancelled without a new one. A pulled or faded front wall still waits replan_cooldown_s first (replan_after_front_pull). Each case is logged and notified with the old and new entry, stop and leverage.

Example

On: a short rests at 2746.86 with walls at 2746.85-2748.22 and 2748.22-2749.59, stop 2757.74 at 105x. At 16:15:33 the far wall fades: the bot re-plans from the near wall alone, entry 2746.86, stop 2756.46 (0.3% behind 2748.22), and the leverage that still keeps liquidation behind that stop, then replaces the order.

When to change it

Leave it on. Turn it off to keep a resting entry's plan until it fills or is cancelled for another reason.

Higher, lower, on or off

On: the stop of a resting entry always sits behind walls that still exist, often tighter. Off: a resting entry keeps a stop planned behind a wall that is gone.

Risk notes

Low: each re-plan loses the order's place in the queue, so a few fills may be missed.

Minimum reward/risk

min_reward_risk

Default
1
Range
0 to 20
Type
Number
Live confirmation
No. Changes apply in every mode without the typed confirmation.

In the dashboard: Skip a setup whose (take-profit distance - round-trip fees) / stop distance is below this. Setups without a counter wall are allowed and run on stop + trailing only.

What it does

Skips a setup whose reward/risk is too low. Reward is the distance to the take profit minus round-trip fees; risk is the distance from entry to stop. Setups with no counter wall are still allowed and run on stop and trailing only.

Example

Long entry 60000, stop 59700 (300), TP 60450 (450). Fees in price: 60000 x 0.02% + 60450 x 0.05% = 42.2. Reward/risk = (450 - 42.2) / 300 = 1.36, which passes 1.0.

When to change it

Raise it to take only setups with more room to the counter wall. 0 disables the check.

Higher, lower, on or off

Higher: fewer entries, each with more distance to the take profit relative to the stop. Lower: more entries, including ones where the counter wall is close.

Risk notes

Low: it only blocks entries. Only active with entry_model wall_hug and tp_mode counter_wall.

Allow long and short on one coin

allow_both_sides I ACCEPT in live

Default
Off
Range
On or off
Type
On/off
Live confirmation
Yes: switching it on in live mode asks you to type I ACCEPT.

In the dashboard: Needs a Binance account in Hedge Mode (paper and backtests simulate one): one LONG and one SHORT on the same coin at once, each with its own margin, stop, take profit and PnL. Never two trades on the same side. Ignored in One-way Mode. The second side must use the leverage already set on the coin (Binance leverage is per coin, not per side).

What it does

Allows one LONG and one SHORT on the same coin at the same time, each with its own margin, stop, take profit and PnL. Needs a Binance account in Hedge Mode; paper mode and backtests simulate one. Never two trades on the same side. Ignored in One-way Mode.

Example

BTC has a long open off a bid wall at 60000 and a confirmed ask wall appears at 60800. On (Hedge Mode): a short can be planned there too. Off: the wall note says the long side already has an open trade and "allow_both_sides is off".

When to change it

Turn on if you run Hedge Mode and want both walls on a coin traded.

Higher, lower, on or off

On: up to two trades per coin (one per side), still limited by max_positions. Off: one trade per coin.

Risk notes

Medium to high: more exposure per coin. The second side must use the leverage already set on the coin, because Binance leverage is per coin, not per side.

S/R rule for wall stacks

sr_stack_rule

Default
any
Choices
any, nearest
Type
Choice
Live confirmation
No. Changes apply in every mode without the typed confirmation.

In the dashboard: With the S/R filter on: a stack passes if any of its walls (or only the nearest) is at a higher-timeframe level.

What it does

Decides how the support/resistance check treats a stack of walls. With any, the bot checks the walls of the stack from the nearest outward and passes as soon as one of them sits at a higher-timeframe level. With nearest, only the nearest wall of the stack is checked.

Example

A long stack has walls at 59,400 and 59,100 USDT, and the only 4h level is at 59,080. With any, the 59,100 wall matches and the entry is evaluated. With nearest, only 59,400 is checked, it has no level, and the stack is skipped.

When to change it

Switch to nearest if you want the wall the entry is actually placed in front of to be the one backed by a level.

Higher, lower, on or off

any: more stacks pass, because any wall in the stack can supply the level. nearest: fewer stacks pass; the level must be at the front wall.

Risk notes

Only matters when sr_filter is on and the wall hug entry model builds stacks (entry_anchor = stack). With a single wall there is nothing to choose between.

Wall hug leverage cap

hug_max_leverage I ACCEPT in live

Default
0 x
Range
0 to 125 x
Type
Whole number
Unit
x
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: Wall hug only. 0 = no cap: use the highest leverage the exchange allows. Any other value caps the leverage search at that value.

What it does

Wall hug only. 0 means no cap: the leverage search starts at the highest leverage the exchange allows. Any other value caps the search at that number. The coin scanner also uses it when checking minimum position size.

Example

BTC allows 125x. At 0 the bot tries 125x first and steps down until all checks pass. At 50, it starts at 50x and only goes lower if a check fails.

When to change it

Set a cap if you want a firm upper limit on leverage, or in paper mode without an API key, where leverage brackets are only assumed.

Higher, lower, on or off

Higher (or 0): the highest leverage that passes the liquidation, fee and size checks. Lower: smaller positions for the same margin, liquidation further away.

Risk notes

High: raising it allows larger positions and liquidation closer to entry. Very high leverage also makes the liquidation buffer and fees matter more.

Entry ticks in front of wall

entry_ticks

Default
1 ticks
Range
0 to 50 ticks
Type
Whole number
Unit
ticks
Live confirmation
No. Changes apply in every mode without the typed confirmation.

In the dashboard: Wall hug only. The entry rests this many ticks in front of the wall's nearest level.

What it does

Wall hug entry model only. The entry order rests this many ticks in front of the near edge of the wall's core (above a support wall for a long, below a resistance wall for a short).

Example

A support wall's core starts at 0.5000 and the tick is 0.0001. With 1 tick, the long entry rests at 0.5001. With 3 ticks it rests at 0.5003.

When to change it

Raise it if entries keep missing because other traders queue in front of you at the wall. Lower it (even to 0) to sit as close to the wall as possible.

Higher, lower, on or off

Higher: more likely to fill, but further from the wall, so a stop behind the wall costs more and the bot may need lower leverage. Lower: closer to the wall and a smaller loss at the stop, but price often turns before reaching your order.

Risk notes

Moderate. If the entry would already be at or past the best price on the other side, the plan is refused ("would chase") instead of placed. Not used by the loss_budget entry model.

Leverage mode

leverage_mode used only with entry_model loss_budget

Default
fixed
Choices
fixed, auto
Type
Choice
Live confirmation
No. Changes apply in every mode without the typed confirmation.

In the dashboard: Fixed uses the leverage below for every trade. Auto picks, for each wall, the highest leverage up to the cap that passes every safety check (liquidation cushion, loss target, exchange minimum, leverage brackets).

What it does

Loss budget entry model only (the default wall hug model picks its own leverage). fixed uses leverage for every trade. auto tries from leverage_cap downward and uses the highest leverage that passes every check (liquidation cushion, loss target, exchange minimum size, leverage brackets).

Example

In auto with cap 50, the bot tries 50x, then 49x, and so on. If 50x to 41x put the stop too close to liquidation, it uses 40x and logs why 41x failed.

When to change it

Only if entry_model is loss_budget. Use auto to let each wall decide; use fixed for predictable sizing.

Higher, lower, on or off

fixed: always leverage (capped by the coin's maximum). auto: the highest passing leverage up to leverage_cap, so it often runs at the cap.

Risk notes

Moderate. auto tends to choose high leverage, which puts liquidation closer to entry.

Leverage

leverage I ACCEPT in live used only with entry_model loss_budget and leverage_mode fixed

Default
50 x
Range
1 to 125 x
Type
Whole number
Unit
x
Live confirmation
Yes: raising it in live mode asks you to type I ACCEPT.

In the dashboard: Capped per coin by the exchange's own maximum.

What it does

The leverage used in the loss budget model when leverage_mode is fixed. If the exchange allows less on a coin, that coin's maximum is used. Not used by the wall hug model.

Example

50x with 2 USDT margin gives a 100 USDT position. On a coin that allows only 20x, the bot uses 20x and the position is 40 USDT.

When to change it

Only with entry_model loss_budget and leverage_mode fixed. Lower it if trades are refused for liquidation being too close to the stop.

Higher, lower, on or off

Higher: bigger position from the same margin, so the entry sits closer to the stop for the same loss target, and liquidation is closer. Lower: smaller position, more room, but entries sit further from the wall.

Risk notes

High. Leverage sets how close liquidation is. The bot still refuses plans whose stop is too near the estimated liquidation.

Leverage cap

leverage_cap I ACCEPT in live used only with entry_model loss_budget and leverage_mode auto

Default
50 x
Range
1 to 125 x
Type
Whole number
Unit
x
Live confirmation
Yes: raising it in live mode asks you to type I ACCEPT.

In the dashboard: In auto mode, the bot never exceeds this even if the exchange allows more.

What it does

The highest leverage auto leverage mode may use in the loss budget model, even if the exchange allows more. Not used by the wall hug model (that uses its own wall hug leverage setting).

Example

Cap 50 on a coin that allows 125x: auto starts trying at 50x and steps down from there. Cap 20: it starts at 20x.

When to change it

Lower it if you want auto to stay at gentler leverage.

Higher, lower, on or off

Higher: auto can pick bigger leverage, bigger positions and closer liquidation. Lower: positions stay smaller and liquidation further away, but some walls may fail the minimum-size check.

Risk notes

High when raised: auto usually chooses the highest leverage that passes, so the cap is often the leverage actually used.

Margin per entry

margin_pct I ACCEPT in live

Default
2 %
Range
0.1 to 25 %
Type
Number
Unit
%
Live confirmation
Yes: raising it in live mode asks you to type I ACCEPT.

In the dashboard: Share of the futures balance used as margin for each entry.

What it does

The share of the sizing base used as margin for each new entry. The base depends on sizing_base (by default your available balance plus the margin held by Wallbot's own pending entries), and the live balance cap applies after that.

Example

Margin 10% with 20 USDT available and 6 USDT held by your own pending entries: base 26, margin 2.60 USDT per entry. At 50x that is a 130 USDT position.

When to change it

Raise it if entries are refused as below the exchange minimum. Lower it to risk less per trade.

Higher, lower, on or off

Higher: bigger positions and bigger losses per stop-out. Lower: smaller positions, but small accounts may fall below the exchange's minimum order size.

Risk notes

High. Each stop-out loses a share of this margin, and several trades can be open or pending at once (max_positions).

Entry order timeout

pending_timeout_s I ACCEPT in live

Default
300 s
Range
0 to 86400 s
Type
Whole number
Unit
s
Live confirmation
Yes: raising it in live mode asks you to type I ACCEPT.

In the dashboard: Cancel an unfilled entry after this long. 0 = no time limit: the entry rests until another rule cancels it (wall pulled or faded, re-plan, side switch, entry_cancel_far_atr_mult, entry_max_age_s, ...).

What it does

An entry order that has not filled after this many seconds is cancelled. The check runs about once a second. 0 = no time limit: the entry rests until another rule cancels it (wall pulled or faded, a re-plan to a closer wall, a side switch, Cancel entries far from price, Entry maximum age).

Example

At 300: an entry placed at 10:00:00 that is still unfilled is cancelled at about 10:05:00, which frees its margin and its max_positions slot. On 8788 (data since 10-29) the same entry is usually placed again on the same wall within a second.

When to change it

Raise it, or set 0 with Cancel entries far from price on, if entries are often cancelled just before price reaches the wall. Lower it to free slots for fresher walls.

Higher, lower, on or off

Higher or 0: entries wait longer and fill more often, with fewer cancel/re-place requests, but can fill on a wall that has changed since. Lower: stale entries are cleared quickly, but fewer fill.

Risk notes

Low to moderate. Waiting entries hold margin and a slot until cancelled. In live, raising it or setting 0 asks for I ACCEPT.

Cancel entries far from price

entry_cancel_far_atr_mult I ACCEPT in live

Default
0 x ATR
Range
0 to 50 x ATR
Type
Number
Unit
x ATR
Live confirmation
Yes: raising it in live mode asks you to type I ACCEPT.

In the dashboard: Cancel a resting entry when the price has moved more than this many ATR(14) of 15-minute candles away from it (checked about every second; the ATR is refreshed every 5 minutes per coin). 0 = off.

What it does

Cancels a resting entry when the price has moved more than this many ATR(14) of 15-minute candles away from the entry price. The ATR is fetched once every 5 minutes per coin while an entry rests (only when this is on). 0 = off.

Example

At 2 with a 15-minute ATR of 0.8%: a long entry resting 1.6% below the price is kept; once the price is 1.7% above it, the entry is cancelled.

When to change it

With no time limit (Entry order timeout 0): it clears entries the market has walked away from.

Higher, lower, on or off

Lower: entries are cancelled sooner when the price drifts away; higher: they rest longer.

Risk notes

Low. It only cancels; missing data (no book or ATR) cancels nothing. In live, raising it or turning it off asks for I ACCEPT.

Entry maximum age

entry_max_age_s I ACCEPT in live

Default
0 s
Range
0 to 604800 s
Type
Whole number
Unit
s
Live confirmation
Yes: raising it in live mode asks you to type I ACCEPT.

In the dashboard: Last-resort limit: cancel a resting entry older than this, whatever else happens. 0 = off.

What it does

A last-resort limit: a resting entry older than this is cancelled whatever else happens. 0 = off.

Example

At 14400: an entry still unfilled 4 hours after it was placed is cancelled.

When to change it

With no time limit, so that no entry rests for days.

Higher, lower, on or off

Lower: entries never rest long; higher: rare old entries can still fill.

Risk notes

Low. It only cancels. In live, raising it or turning it off asks for I ACCEPT.

Require a higher-timeframe level

sr_filter

Default
On
Range
On or off
Type
On/off
Live confirmation
No. Changes apply in every mode without the typed confirmation.

In the dashboard: Only trade a wall that sits within the tolerance of a support/resistance level from higher-timeframe pivots: a support wall needs a level at or below price, a resistance wall one at or above price.

What it does

Only trade a wall that sits near a support/resistance level found from higher-timeframe pivots. A support (bid) wall needs a level at or below price, a resistance (ask) wall one at or above price, within sr_tolerance_pct of the wall's zone.

Example

A bid wall at 59,400 to 59,430 USDT, price 60,000, tolerance 0.3%. A 4h level at 59,300 is about 0.17% from the wall, so it passes. If the nearest level below price were 58,900 (about 0.85% away), the wall is skipped.

When to change it

Turn off to trade every confirmed wall, regardless of chart levels.

Higher, lower, on or off

On: fewer trades, only walls backed by a chart level. Off: all confirmed walls can be traded.

Risk notes

In the simulator feed and in backtests without candle history, the filter is skipped with a warning. If candles cannot be loaded, the wall is skipped.

24h high/low as a level

level_24h_mode I ACCEPT in live Watch (log only): shadow_level_24h_mode

Default
off
Choices
off, extra_level, strict
Type
Choice
Live confirmation
Yes: any change in live mode asks you to type I ACCEPT.

In the dashboard: off: only the higher-timeframe levels count. extra_level: a support wall at the 24h low (resistance at the 24h high) also passes the level filter. strict: only walls at the 24h low/high pass (works even with the level filter off). Same tolerance as the levels; 1h candles, refreshed hourly, the current price counts. The charts show '24h H' and '24h L' while this or its watch switch is on.

What it does

Uses the 24h high and low (from 1h candles, refreshed hourly, the current price counts as a new extreme) as levels. off: only the higher-timeframe levels. extra_level: a support wall at the 24h low (resistance at the 24h high), within the level tolerance, also passes the level filter. strict: only walls at the 24h low/high pass, even with the level filter off. While this or shadow_level_24h_mode is on, both charts show "24h H" and "24h L".

Example

BTC 24h low 81,200, tolerance 0.3%: a support wall at 81,350-81,380 is 0.18% from it and passes in extra_level and strict; with no 4h level nearby it would be skipped in off.

When to change it

Only if the watch data shows walls at 24h extremes do better. On 8788 (416 fills) fills near a 24h extreme won 29% vs 38% elsewhere, and the extra setups would mostly not fill or hit the stop.

Higher, lower, on or off

off: unchanged. extra_level: more entries (walls at 24h extremes without a 4h level). strict: far fewer entries, only at 24h extremes.

Risk notes

Medium: changes which walls are traded.

Level timeframe

sr_timeframe

Default
4h
Choices
1h, 4h, 1d
Type
Choice
Live confirmation
No. Changes apply in every mode without the typed confirmation.

In the dashboard: Candle size used to find pivot levels.

What it does

The candle size used to find the pivot levels for the support/resistance filter.

Example

With 4h and a 30 day lookback, the bot looks at about 180 closed 4h candles. With 1h it looks at about 720 candles, which gives more, finer levels.

When to change it

Use 1h for more and closer levels, 1d for fewer but more important levels.

Higher, lower, on or off

1h: many levels, the filter passes more walls. 4h: a middle ground. 1d: few, strong levels, the filter passes fewer walls.

Risk notes

Low: only changes which walls pass sr_filter. Has no effect when sr_filter is off. prefer_near_4h_level always uses 4h.

Level lookback

sr_lookback_days

Default
30 days
Range
1 to 365 days
Type
Whole number
Unit
days
Live confirmation
No. Changes apply in every mode without the typed confirmation.

In the dashboard: How far back pivots are collected.

What it does

How far back, in days, closed candles are collected to find pivot levels. Also used by prefer_near_4h_level.

Example

30 days on 4h candles is about 180 candles. With 7 days only about 42 candles are used, so older levels are ignored.

When to change it

Shorten it to use only recent levels. Lengthen it to include older levels.

Higher, lower, on or off

Higher: more levels from further back, the filter passes more walls. Lower: only recent levels.

Risk notes

Low. Very long lookbacks add many old levels, which makes the filter less selective.

Pivot strength

sr_pivot_strength

Default
2 candles
Range
1 to 10 candles
Type
Whole number
Unit
candles
Live confirmation
No. Changes apply in every mode without the typed confirmation.

In the dashboard: A pivot high (low) must be higher (lower) than this many candles on each side.

What it does

A candle is a pivot high when its high is strictly above the highs of this many candles on each side (a pivot low mirrors it). A pivot only counts once those right-hand candles have closed.

Example

With 2, a 4h high counts as a pivot if it is above the 2 candles before and the 2 after, and it is known only 8 hours (2 candles) after that candle closed.

When to change it

Raise it for fewer, more significant levels. Lower it for more levels.

Higher, lower, on or off

Higher: fewer levels, each confirmed later. Lower: more levels, the filter passes more walls.

Risk notes

Low. Only changes the levels used by sr_filter and prefer_near_4h_level.

Level tolerance

sr_tolerance_pct

Default
0.3 %
Range
0.01 to 5 %
Type
Number
Unit
%
Live confirmation
No. Changes apply in every mode without the typed confirmation.

In the dashboard: Pivots this close together form one level, and a wall must be this close to a level.

What it does

Two jobs. Pivots this close together are merged into one level (their average). And a wall must be within this distance of a level to pass the support/resistance filter (measured from the wall's zone edges, 0 if the level is inside the zone).

Example

Level at 59,300 USDT, bid wall zone 59,400 to 59,430. Distance (59,400 - 59,300) / 59,300 is about 0.17%. With 0.3% the wall passes; with 0.1% it is skipped.

When to change it

Widen it if good walls are rejected for being just off a level. Narrow it to demand walls right at the level.

Higher, lower, on or off

Higher: more walls pass, and nearby pivots merge into fewer levels. Lower: stricter matching, more separate levels.

Risk notes

Low. A very wide tolerance makes the filter pass almost everything.

Level tolerance mode

sr_tolerance_mode

Default
fixed_pct
Choices
fixed_pct, atr
Type
Choice
Live confirmation
No. Changes apply in every mode without the typed confirmation.

In the dashboard: Fixed uses the level tolerance above for every coin. ATR follows each coin's volatility: the ATR multiple below times ATR(14) of the coin's level-timeframe candles as % of price, kept between the minimum and maximum; recomputed when a new candle closes.

What it does

How the level tolerance is set. fixed_pct: sr_tolerance_pct for every coin (the behaviour before this setting existed). atr: each coin gets its own tolerance from its volatility: sr_tol_atr_mult times ATR(14) of its level-timeframe candles (4h by default) as % of price, kept between sr_tol_min_pct and sr_tol_max_pct. It is recomputed when a new candle closes. The tolerance is used in three places: merging nearby swing points into levels, matching a wall to a level in the level filter, and the bands on both charts. The chart legends show the coin's current value, e.g. "±0.08%".

Example

A calm coin with ATR(14) 0.8% of price: 0.1 x 0.8% = 0.08%. A wild coin with ATR 7%: 0.7%, capped at 0.5%. A very quiet coin with ATR 0.3%: 0.03%, raised to 0.05%. In fixed_pct all three use 0.3%.

When to change it

Use atr when one fixed tolerance is too loose for calm coins (walls pass far from any level) and too tight for volatile ones (good walls just off a level are skipped).

Higher, lower, on or off

fixed_pct: one tolerance for every coin. atr: tighter matching and more separate levels on calm coins, looser on volatile ones. Coins without enough candles fall back to sr_tolerance_pct.

Risk notes

Low to moderate. It changes which walls pass the level filter; check the log lines "no 4h level ... within X%" after switching.

Level tolerance ATR multiple

sr_tol_atr_mult

Default
0.1
Range
0.01 to 2
Type
Number
Live confirmation
No. Changes apply in every mode without the typed confirmation.

In the dashboard: ATR mode: the tolerance is this multiple of ATR(14) as % of price.

What it does

In atr tolerance mode: the tolerance is this multiple of ATR(14) of the level-timeframe candles, as % of price.

Example

ATR(14) 1.5% of price, multiple 0.1: tolerance 0.15%. Multiple 0.2: 0.3%.

When to change it

Raise it if too few walls pass the level filter in atr mode; lower it to demand walls closer to the level.

Higher, lower, on or off

Higher: wider bands, more walls pass, more pivots merge. Lower: the reverse. Always kept between the minimum and the maximum.

Risk notes

Low.

Level tolerance minimum

sr_tol_min_pct

Default
0.05 %
Range
0.01 to 5 %
Type
Number
Unit
%
Live confirmation
No. Changes apply in every mode without the typed confirmation.

In the dashboard: ATR mode: the tolerance is never below this.

What it does

In atr tolerance mode: the tolerance is never below this, however calm the coin.

Example

ATR 0.3% x 0.1 = 0.03%, raised to the minimum 0.05%.

When to change it

Raise it if calm coins end up with bands so thin that walls almost never sit inside them.

Higher, lower, on or off

Sets the floor of the per-coin tolerance.

Risk notes

Low.

Level tolerance maximum

sr_tol_max_pct

Default
0.5 %
Range
0.01 to 5 %
Type
Number
Unit
%
Live confirmation
No. Changes apply in every mode without the typed confirmation.

In the dashboard: ATR mode: the tolerance is never above this.

What it does

In atr tolerance mode: the tolerance is never above this, however volatile the coin. If it is set below the minimum, the minimum is used.

Example

ATR 7% x 0.1 = 0.7%, capped at the maximum 0.5%.

When to change it

Lower it so very volatile coins still need a wall reasonably close to a level.

Higher, lower, on or off

Sets the ceiling of the per-coin tolerance.

Risk notes

Low. A high maximum lets the filter pass almost anything on volatile coins.

Wall retry cooldown

wall_retry_cooldown_s

Default
30 s
Range
0 to 3600 s
Type
Number
Unit
s
Live confirmation
No. Changes apply in every mode without the typed confirmation.

In the dashboard: After a wall is tried (planned or skipped), it is not tried again for this long.

What it does

Once the bot starts working on a wall as an entry anchor (it plans an entry or skips it after its checks), the same wall on the same coin and book source is not tried again until this time has passed. This stops the bot from re-checking and logging the same wall on every book update.

Example

Cooldown 30 s: a wall at 2,450 is checked at 10:00:00 and skipped because of a support/resistance rule. It is not checked again before 10:00:30, even if the book updates hundreds of times in between.

When to change it

Lower it if conditions change fast and you want a skipped wall re-checked sooner. Raise it to quieten the log or save requests.

Higher, lower, on or off

Higher: fewer repeat checks and log lines, but a wall that becomes acceptable is picked up later. Lower: faster second chances, more checks, more log noise and possibly more requests.

Risk notes

Low. Very low values can make the bot busy on a single wall.

Closer-wall re-plan interval

replan_min_interval_s

Default
30 s
Range
0 to 3600 s
Type
Number
Unit
s
Live confirmation
No. Changes apply in every mode without the typed confirmation.

In the dashboard: At most one closer-wall re-plan per coin and side within this time.

What it does

While an entry is pending, a new confirmed wall may appear between price and the entry (a higher bid wall for a long, a lower ask wall for a short). The bot can then re-plan the entry in front of that closer wall. This setting allows at most one such re-plan per coin and side in this time.

Example

Interval 30 s: a long on ETH was re-planned at 14:00:00. A new closer wall appears at 14:00:12, so the bot notes "re-plan limit" and, with replan_recheck_after_limit on, re-checks at 14:00:30.

When to change it

Raise it if entries hop around too often on books with many walls. Lower it if you want entries to follow closer walls faster.

Higher, lower, on or off

Higher: fewer cancel-and-replace cycles, the entry may sit behind a closer wall for longer. Lower: entries follow closer walls quickly, more order traffic. 0: no limit.

Risk notes

Low to medium. Each re-plan cancels and places an order; very low values mean more requests and more chances for cancel races.

Deeper walls tried at most

rr_deeper_max_walls

Default
3
Range
1 to 10
Type
Whole number
Live confirmation
No. Changes apply in every mode without the typed confirmation.

In the dashboard: rr_try_deeper_wall: how many deeper walls are evaluated (each runs every entry check).

What it does

rr_try_deeper_wall: how many deeper walls are evaluated, nearest first. Each evaluation runs the full entry checks, including one account check on the exchange.

Example

At 3 with 5 deeper walls in range, only the 3 nearest are tried.

When to change it

Lower it to limit exchange requests; raise it to reach farther walls.

Higher, lower, on or off

Higher: more candidates, more requests. Lower: fewer.

Risk notes

Low.

Watch: try deeper walls

shadow_rr_try_deeper_wall

Default
Off
Range
On or off
Type
On/off
Live confirmation
No. Changes apply in every mode without the typed confirmation.

In the dashboard: Log (and record in the learning log) what rr_try_deeper_wall would try when the nearest wall fails reward/risk, with an approximate reward/risk; nothing is placed. The paper shadow copies live entries and cannot place entries of its own, so this is a log-only watch.

What it does

On the trading instance, logs what rr_try_deeper_wall would do: when the nearest wall fails reward/risk, "[watch] rr_try_deeper_wall would try the deeper wall ... approx. reward/risk 1.84" with an approximate reward/risk (stop behind the deeper wall, same take profit; the other checks are not run). Also recorded in the learning log (category rr_deeper_watch). Nothing is placed. The paper shadow copies the live entries and cannot place its own, so this is a log-only watch.

Example

Live off, watch on: 244 reward/risk skips in 5 days would give about 244 watch lines, each with the deeper wall and its approximate reward/risk.

When to change it

Turn it on to collect data before deciding on rr_try_deeper_wall.

Higher, lower, on or off

On: log lines only. Off: none.

Risk notes

None for trading.

Watch: 24h high/low as a level

shadow_level_24h_mode

Default
off
Choices
off, extra_level, strict
Type
Choice
Live confirmation
No. Changes apply in every mode without the typed confirmation.

In the dashboard: Log what level_24h_mode extra_level or strict would accept or skip while level_24h_mode is off; nothing is placed (log-only, like the other watch switches).

What it does

While level_24h_mode is off, logs what extra_level or strict would do: "[watch] level_24h_mode extra_level would accept the wall ... at the 24h low ..." or "strict would skip ...". Recorded in the learning log (level_24h_watch). off: no watch. Nothing is placed; log-only, because the paper shadow copies live entries and cannot place its own.

Example

Watch extra_level on 8788: about 216 extra walls in 5 days would have been accepted at a 24h extreme.

When to change it

Turn it on to measure a 24h mode before using it.

Higher, lower, on or off

off: nothing. extra_level / strict: watch lines for that mode; the charts show 24h H/L.

Risk notes

None for trading.

Opposite entry after a take profit

tp_opposite_priority

Default
On
Range
On or off
Type
On/off
Live confirmation
No. Changes apply in every mode without the typed confirmation.

In the dashboard: After a take profit fills at a counter wall, that wall gets priority for an opposite entry (a short in front of the resistance after a long, and the reverse) for the window below: no per-wall cooldown, no same-side entry may take the coin's slot, and the entry is placed on the first book update where the wall is still valid, the post-only entry would rest (no chasing) and every other check passes. If the wall is broken, pulled, faded, absorbed, below the size rules or below the minimum remaining size, the window ends at once and normal rules apply.

What it does

After a take profit fills in front of a counter wall, that same wall gets priority for an opposite entry: a short in front of the resistance after a long, a long in front of the support after a short. During the window (tp_opposite_priority_s) there is no per-wall retry cooldown for it, no same-side entry on that coin may take the slot, and it is re-checked on every book update.

Example

A long closes at its take profit 91.27, 2 ticks below a resistance wall at 91.29-91.33. Right at the fill price sits on the planned short entry, so the post-only order would cross: it waits. 4 s later price is at 91.20: the wall is still confirmed, still big enough and holds 80% of its size before the first touch (minimum 50%), so the short is placed at once instead of after the 30 s wall_retry_cooldown_s.

When to change it

Leave it on to trade the bounce off the wall that just took your profit. Turn it off if you prefer every wall, including this one, to wait for the normal retry cooldown and compete equally with the other walls.

Higher, lower, on or off

On: the counter wall is tried first and fastest for the window, and same-side entries wait. Off: normal rules; the opposite entry usually waits for the wall retry cooldown and a re-entry on the original side can take the slot first.

Risk notes

Medium. It flips direction quickly after a win. Every safety check still applies and the wall is re-checked at the moment of placing (broken, pulled, faded, absorbed, size rules, remaining size); an invalid wall ends the window and nothing is sent to the exchange for a refused check.

Opposite-entry priority window

tp_opposite_priority_s

Default
90 s
Range
1 to 3600 s
Type
Number
Unit
s
Live confirmation
No. Changes apply in every mode without the typed confirmation.

In the dashboard: How long the counter wall keeps priority after the take profit filled.

What it does

How long the counter wall keeps its priority after the take profit filled. When the window ends without an entry, normal entry rules apply again.

Example

Default 90: a take profit fills at 10:00:00; until 10:01:30 only the counter wall may open the opposite entry on this coin and same-side walls are held back. At 10:01:30 the window ends and the next wall that passes the normal rules can be used.

When to change it

Shorter if the coin moves fast and a bounce that has not happened within a minute is unlikely; longer for slower coins where price often hovers at the wall for a few minutes.

Higher, lower, on or off

Higher: the counter wall keeps priority longer and same-side entries wait longer. Lower: the priority ends sooner and normal rules take over earlier.

Risk notes

Low. It only changes which wall may be used first and for how long; it never skips a safety check.

Counter wall minimum remaining size

tp_flip_min_remaining_pct

Default
50 %
Range
1 to 100 %
Type
Number
Unit
%
Live confirmation
No. Changes apply in every mode without the typed confirmation.

In the dashboard: The counter wall must still hold at least this share of the size it had just before price first touched it, at the moment the opposite entry is placed.

What it does

The counter wall must still hold at least this share of the size it had just before price first touched it (recorded at the first touching trade) when the opposite entry is placed. A wall that has been eaten down is likely to break.

Example

The resistance wall held 1,000 HYPE just before the first touch. With 50%: at 620 HYPE left the short may be placed; at 430 HYPE left the priority ends with "only 43% of its size just before the first touch is left" and no entry is sent.

When to change it

Raise it (for example to 70) to only flip on walls that are barely eaten. Lower it to also trade walls that have absorbed a lot of volume.

Higher, lower, on or off

Higher: fewer opposite entries, only on walls that are still mostly intact. Lower: more opposite entries, including on walls that have been eaten down.

Risk notes

Medium at low values: an eaten-down wall breaks more easily, and the stop behind it is then hit.

Failed counter wall must re-confirm

tp_flip_reconfirm

Default
On
Range
On or off
Type
On/off
Live confirmation
No. Changes apply in every mode without the typed confirmation.

In the dashboard: When the counter wall fails a validity check during the opposite-entry priority window (broken, pulled, faded, absorbed, below the size rules or below the minimum remaining size), it is used for no new entry at all until it confirms again from scratch, as a new wall (a full persistence period).

What it does

A counter wall that fails any validity check during the opposite-entry priority window (for example it holds less than tp_flip_min_remaining_pct of its pre-touch size) is treated as a new wall: unconfirmed, with a fresh persistence period. It is used for no new entry, on either side, until it confirms again from scratch.

Example

The take profit fills at 91.316 in front of a wall at 91.31-91.356 that held 1,000 HYPE before the first touch. 2 s later only 400 HYPE are left (40%, minimum 50%): no short, the window ends, and the wall must stay big enough for another wall_persist_s (45 s) as a new wall. Until then it is not traded, even after the window is over.

When to change it

Leave it on: a wall that was just eaten down or failed the checks is not a reliable anchor. Turn it off only if you want normal rules to be able to use such a wall again as soon as the window ends.

Higher, lower, on or off

On: the failed wall is out of play until it re-confirms (a full persistence period). Off: once the window ends, normal rules may trade the wall straight away if it is still confirmed.

Risk notes

Low. It only blocks entries on a wall that already failed a check; it never opens anything.

Sizing base

sizing_base

Default
available_plus_own_pending
Choices
available_plus_own_pending, available
Type
Choice
Live confirmation
No. Changes apply in every mode without the typed confirmation.

In the dashboard: Margin per entry = margin % x this base. available_plus_own_pending: the exchange's available balance plus the margin held by Wallbot's own pending entry orders (open positions, manual orders/positions, fees and funding still reduce it), so pending entries don't shrink the next one. available: the available balance alone. The balance cap (live safety) applies after this.

What it does

The balance that margin_pct is taken from. Margin of open positions, manual orders or positions, fees and funding always reduce it. The live balance cap, if set, applies afterwards (the smaller of base and cap).

Example

Margin 10%, 20 USDT available, 6 USDT in your own pending entries. available_plus_own_pending: base 26, margin 2.60 USDT. available: base 20, margin 2.00 USDT.

When to change it

Use available if you want each new entry to shrink as more entries are waiting.

Higher, lower, on or off

available_plus_own_pending: available balance plus margin held by Wallbot's own pending entries, so waiting entries do not shrink the next one. available: the available balance alone, so each pending entry makes the next one smaller.

Risk notes

Moderate. With available_plus_own_pending, several pending entries can together need more than the free balance; require_free_margin then skips the ones that do not fit.

Require free margin to open

require_free_margin

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 new entry is only placed if the exchange's free balance (already reduced by positions and pending orders) covers the planned margin plus a fee buffer; otherwise it is skipped with the reason. The order is never shrunk to fit: full size or nothing.

What it does

Before placing a new entry, the bot reads the exchange's free balance (already reduced by positions and pending orders). If it is below the planned margin x (1 + free_margin_buffer_pct), the entry is skipped with the reason. The order is never shrunk to fit.

Example

Planned margin 2.60 USDT, buffer 5%: it needs 2.73 USDT free. With 2.70 USDT free the entry is skipped and the log shows need, free, and what pending and open trades hold.

When to change it

Keep it on. Turn it off only for testing.

Higher, lower, on or off

On: full size or nothing, skipped entries are logged. Off: the entry is sent anyway and the exchange may reject it for insufficient margin.

Risk notes

Moderate when off: orders can be rejected by the exchange. If the free balance cannot be read, the entry is skipped either way.

Free margin buffer

free_margin_buffer_pct

Default
5 % of the margin
Range
0 to 100 % of the margin
Type
Number
Unit
% of the margin
Live confirmation
No. Changes apply in every mode without the typed confirmation.

In the dashboard: Extra free balance required on top of the planned margin, for fees.

What it does

Extra free balance required on top of the planned margin before an entry is placed, to leave room for fees. Used only when require_free_margin is on.

Example

At 5% with a planned margin of 2.00 USDT: at least 2.10 USDT must be free. With 2.05 USDT free, the entry is skipped.

When to change it

Raise it if entries still get rejected for margin after passing the check. Lower it to fit entries more tightly.

Higher, lower, on or off

Higher: more entries are skipped, but the ones placed have spare balance for fees. Lower: more entries fit, with less spare.

Risk notes

Low. At 0 an entry may be sent with no room left for its fees.

Re-check closer walls after the re-plan limit

replan_recheck_after_limit

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 closer confirmed wall that appears within the re-plan limit (30 s after the last re-plan) is re-checked when the limit expires, instead of being ignored until another wall confirms.

What it does

A closer confirmed wall that appears within the re-plan limit (replan_min_interval_s, 30 seconds after the last re-plan) is checked again when the limit runs out, instead of being ignored until some other wall confirms.

Example

A long was re-planned at 12:00:00. At 12:00:20 a closer bid wall confirms. On: the log says "re-checking in 10 s" and at 12:00:30 the re-plan is evaluated. Off: the wall is skipped and only reconsidered if another wall confirms later.

When to change it

Leave it on so good closer walls are not missed.

Higher, lower, on or off

On: delayed closer walls get a second look. Off: walls seen during the limit are dropped.

Risk notes

Low: affects which walls are used for re-plans, not order safety.

Core: sizing

core_sizing_mode I ACCEPT in live

Default
inherit
Choices
inherit, pct_balance, fixed_margin_usdt, fixed_risk_usdt
Type
Choice
Live confirmation
Yes: any change in live mode asks you to type I ACCEPT.

In the dashboard: Position size of new Core entries. inherit: the global Margin per entry (margin_pct). pct_balance: this % of the sizing balance as margin. fixed_margin_usdt: this many USDT as margin. fixed_risk_usdt: the size whose loss at the stop (fees and planned stop slippage included) equals this many USDT. Exchange minimums, step sizes, leverage and liquidation checks, the free-balance gate and the loss caps apply as always.

What it does

How big new Core entries are. Each group either inherits the global sizing or overrides it. The leverage search, Binance's minimum notional and step sizes, the liquidation-safety checks, the free-balance gate and the loss caps all work exactly as with the global sizing; an entry that comes out too small is skipped with a clear reason.

Example

core_sizing_mode fixed_risk_usdt, core_sizing_value 2: a short with entry 100.00 and stop 100.40 (0.4%), 0.02% maker entry, 0.05% taker stop and 5 bps planned slippage loses about 0.4 + 0.02 + 0.05 + 0.05 = 0.52 USDT per unit, so the size is 3.8 units (380 USDT); at 50x the margin is 7.6 USDT.

When to change it

When Core trades should risk a set amount (fixed_risk_usdt) or use a set margin (fixed_margin_usdt) instead of a share of the balance. Leave it on inherit otherwise.

Higher, lower, on or off

inherit: the global Margin per entry (margin_pct). pct_balance: the value as % of the sizing balance (at most 25). fixed_margin_usdt: the value in USDT as margin. fixed_risk_usdt: the size whose loss at the stop, after fees and the planned stop slippage, equals the value in USDT; margin = position / leverage. A fixed margin or risk never uses more margin than the sizing balance (after the live balance cap).

Risk notes

High when raised: a larger margin or risk loses more per stop-out. In live mode any change of the mode needs I ACCEPT.

Core: sizing value

core_sizing_value I ACCEPT in live

Default
0 % or USDT
Range
0 to 1e+06 % or USDT
Type
Number
Unit
% or USDT
Live confirmation
Yes: raising it in live mode asks you to type I ACCEPT.

In the dashboard: The value for Core sizing: % of the sizing balance (pct_balance, at most 25), or USDT (fixed_margin_usdt, fixed_risk_usdt). Not used with inherit.

What it does

The number for core_sizing_mode: a % of the sizing balance for pct_balance, USDT for fixed_margin_usdt and fixed_risk_usdt. Ignored with inherit.

Example

core_sizing_mode fixed_margin_usdt, value 5: every Core entry uses 5 USDT margin, at 50x a 250 USDT position.

When to change it

Together with the sizing mode.

Higher, lower, on or off

Higher: bigger positions and bigger losses at the stop. Lower: smaller; below the exchange minimum the entry is skipped with the reason.

Risk notes

High when raised; in live mode a higher value needs I ACCEPT.

Movers: sizing

movers_sizing_mode I ACCEPT in live

Default
inherit
Choices
inherit, pct_balance, fixed_margin_usdt, fixed_risk_usdt
Type
Choice
Live confirmation
Yes: any change in live mode asks you to type I ACCEPT.

In the dashboard: Position size of new Movers entries. inherit: the global Margin per entry (margin_pct). pct_balance: this % of the sizing balance as margin. fixed_margin_usdt: this many USDT as margin. fixed_risk_usdt: the size whose loss at the stop (fees and planned stop slippage included) equals this many USDT. Exchange minimums, step sizes, leverage and liquidation checks, the free-balance gate and the loss caps apply as always.

What it does

How big new Movers entries are. Each group either inherits the global sizing or overrides it. The leverage search, Binance's minimum notional and step sizes, the liquidation-safety checks, the free-balance gate and the loss caps all work exactly as with the global sizing; an entry that comes out too small is skipped with a clear reason.

Example

movers_sizing_mode fixed_risk_usdt, movers_sizing_value 2: a short with entry 100.00 and stop 100.40 (0.4%), 0.02% maker entry, 0.05% taker stop and 5 bps planned slippage loses about 0.4 + 0.02 + 0.05 + 0.05 = 0.52 USDT per unit, so the size is 3.8 units (380 USDT); at 50x the margin is 7.6 USDT.

When to change it

When Movers trades should risk a set amount (fixed_risk_usdt) or use a set margin (fixed_margin_usdt) instead of a share of the balance. Leave it on inherit otherwise.

Higher, lower, on or off

inherit: the global Margin per entry (margin_pct). pct_balance: the value as % of the sizing balance (at most 25). fixed_margin_usdt: the value in USDT as margin. fixed_risk_usdt: the size whose loss at the stop, after fees and the planned stop slippage, equals the value in USDT; margin = position / leverage. A fixed margin or risk never uses more margin than the sizing balance (after the live balance cap).

Risk notes

High when raised: a larger margin or risk loses more per stop-out. In live mode any change of the mode needs I ACCEPT.

Movers: sizing value

movers_sizing_value I ACCEPT in live

Default
0 % or USDT
Range
0 to 1e+06 % or USDT
Type
Number
Unit
% or USDT
Live confirmation
Yes: raising it in live mode asks you to type I ACCEPT.

In the dashboard: The value for Movers sizing: % of the sizing balance (pct_balance, at most 25), or USDT (fixed_margin_usdt, fixed_risk_usdt). Not used with inherit.

What it does

The number for movers_sizing_mode: a % of the sizing balance for pct_balance, USDT for fixed_margin_usdt and fixed_risk_usdt. Ignored with inherit.

Example

movers_sizing_mode fixed_margin_usdt, value 5: every Movers entry uses 5 USDT margin, at 50x a 250 USDT position.

When to change it

Together with the sizing mode.

Higher, lower, on or off

Higher: bigger positions and bigger losses at the stop. Lower: smaller; below the exchange minimum the entry is skipped with the reason.

Risk notes

High when raised; in live mode a higher value needs I ACCEPT.

My coins: sizing

pinned_sizing_mode I ACCEPT in live

Default
inherit
Choices
inherit, pct_balance, fixed_margin_usdt, fixed_risk_usdt
Type
Choice
Live confirmation
Yes: any change in live mode asks you to type I ACCEPT.

In the dashboard: Position size of new My coins entries. inherit: the global Margin per entry (margin_pct). pct_balance: this % of the sizing balance as margin. fixed_margin_usdt: this many USDT as margin. fixed_risk_usdt: the size whose loss at the stop (fees and planned stop slippage included) equals this many USDT. Exchange minimums, step sizes, leverage and liquidation checks, the free-balance gate and the loss caps apply as always.

What it does

How big new My coins entries are. Each group either inherits the global sizing or overrides it. The leverage search, Binance's minimum notional and step sizes, the liquidation-safety checks, the free-balance gate and the loss caps all work exactly as with the global sizing; an entry that comes out too small is skipped with a clear reason.

Example

pinned_sizing_mode fixed_risk_usdt, pinned_sizing_value 2: a short with entry 100.00 and stop 100.40 (0.4%), 0.02% maker entry, 0.05% taker stop and 5 bps planned slippage loses about 0.4 + 0.02 + 0.05 + 0.05 = 0.52 USDT per unit, so the size is 3.8 units (380 USDT); at 50x the margin is 7.6 USDT.

When to change it

When My coins trades should risk a set amount (fixed_risk_usdt) or use a set margin (fixed_margin_usdt) instead of a share of the balance. Leave it on inherit otherwise.

Higher, lower, on or off

inherit: the global Margin per entry (margin_pct). pct_balance: the value as % of the sizing balance (at most 25). fixed_margin_usdt: the value in USDT as margin. fixed_risk_usdt: the size whose loss at the stop, after fees and the planned stop slippage, equals the value in USDT; margin = position / leverage. A fixed margin or risk never uses more margin than the sizing balance (after the live balance cap).

Risk notes

High when raised: a larger margin or risk loses more per stop-out. In live mode any change of the mode needs I ACCEPT.

My coins: sizing value

pinned_sizing_value I ACCEPT in live

Default
0 % or USDT
Range
0 to 1e+06 % or USDT
Type
Number
Unit
% or USDT
Live confirmation
Yes: raising it in live mode asks you to type I ACCEPT.

In the dashboard: The value for My coins sizing: % of the sizing balance (pct_balance, at most 25), or USDT (fixed_margin_usdt, fixed_risk_usdt). Not used with inherit.

What it does

The number for pinned_sizing_mode: a % of the sizing balance for pct_balance, USDT for fixed_margin_usdt and fixed_risk_usdt. Ignored with inherit.

Example

pinned_sizing_mode fixed_margin_usdt, value 5: every My coins entry uses 5 USDT margin, at 50x a 250 USDT position.

When to change it

Together with the sizing mode.

Higher, lower, on or off

Higher: bigger positions and bigger losses at the stop. Lower: smaller; below the exchange minimum the entry is skipped with the reason.

Risk notes

High when raised; in live mode a higher value needs I ACCEPT.