Walls and confirmation
A wall is a price zone in the order book that holds far more resting orders than the zones around it. Wallbot only trades a wall after it has stayed in place long enough to be trusted, and it watches every wall closely afterwards. A wall can be pulled, absorbed by trades, fade away, or be broken.
What a wall is
Wallbot keeps a live copy of each watched coin's order book and runs a wall tracker on it. Support walls sit on the bid side, below price. Resistance walls sit on the ask side, above price. A long is planned in front of a support wall, a short in front of a resistance wall. The tracker uses three tests to find a wall.
1. Price levels are grouped into zones
Big orders are often spread over several ticks, so one price level on its own says little. The tracker adds neighbouring levels together into zones wall_bucket_bps wide (default 5 bps, that is 0.05% of price, rounded up to whole ticks). At a price of 101.00 with a 0.01 tick, each zone is 0.05 wide, for example 99.95 to 100.00.
2. The zone must be much bigger than a typical zone
For each side of the book, the tracker takes the median USDT size of all zones within wall_baseline_band_pct (default 5%) of the mid price. This median is the "typical level", or baseline. A zone counts as big enough when both of these hold:
- it is at least
wall_ktimes the baseline (default 8x), and - it is at least
wall_min_usd(default 250,000 USDT). This floor stops thin coins from producing tiny "walls".
3. The zone must sit inside the distance band
A new wall is only picked up between wall_min_dist_pct (0.3%) and wall_max_dist_pct (3%) from price. Closer walls leave no room for an entry. Farther walls are rarely reached. The band only matters when a wall is first found. Once a wall is tracked, price coming closer is exactly what the bot is waiting for, so it never drops a wall for being near.
Example
Illustrative numbers, not a real trade. Price is 101.00. The median bid zone within 5% of price holds 20,000 USDT, so a wall needs at least 8 x 20,000 = 160,000 USDT. The 250,000 USDT floor is higher, so the floor decides. The zone 99.95 to 100.00 holds 957 coins, about 95,700 USDT, so it is not a wall. If 3,000 coins (about 300,000 USDT) rest there, it passes both tests. It is about 1% below price, inside the 0.3% to 3% band, so the tracker starts watching it.
Where the wall really starts and ends
A zone can hold a few small stray orders at its edges. For entries and stops, Wallbot takes the wall's edges from the fewest largest levels that together hold wall_core_pct (default 90%) of the zone's size. The near edge is the core level closest to price, the far edge the one farthest away. Entries, stops and sizing shows how these edges set the entry and the stop.
Confirmation
A big order that appears and vanishes within seconds is the classic spoof. So a newly found wall is only "watching" at first. It must stay big enough for wall_persist_s (default 45 seconds) before it becomes confirmed. This is the main anti-spoofing filter. The ring next to a wall on the dashboard fills up while it waits.
- Only confirmed walls are used for entries, wall stacks, take-profit targets and protection.
- When it confirms, the log says, for example, "Support wall confirmed at 99.95-100 (0.30M USDT)".
- A wall that disappears while still watching is simply dropped. It never had a trade attached.
- With two order-book sources,
wall_confirmationdecides whether a wall must exist on one exchange or on both.
Note. Confirmation lowers the spoof risk but does not remove it. Spoofers can leave a wall up for minutes and pull it when price gets close. That is why every trade keeps watching its wall after the entry.
What happens to a wall
On every book update the tracker compares each wall with its peak size. It also counts how much of any drop was traded (trades printed inside the zone) and how much was cancelled (size that left with no matching trades). If a wall grows to a new peak, both counters start again from zero. A tracked wall ends in one of four ways.
| Outcome | What the tracker saw | What it usually means |
|---|---|---|
| Pulled | The wall fell below wall_vanish_ratio (0.35) of its peak, and at least spoof_cancel_share (0.70) of the drop was cancelled | Likely a spoof: the orders were taken away |
| Absorbed | The wall fell below 0.35 of its peak, but less than 70% of the drop was cancelled | A real wall eaten by trades |
| Faded | The wall slowly stopped standing out (below wall_k x baseline or the USDT floor) for longer than wall_fade_grace_s (10 s), without a big drop | Interest dried up, or the rest of the book grew |
| Broken | Price traded through the zone: for a support wall the best bid went below its low edge, for a resistance wall the best ask went above its high edge | The wall did not hold |
Telling pulled from absorbed
The difference matters because the bot reacts differently. A pull says the wall was never real. An absorption says it was real and buyers or sellers ate through it, which is what the stop exists for.
Example
Illustrative numbers. A support wall peaks at 1,000 coins and drops to 300. That is below 0.35 x 1,000 = 350, so it has vanished. 700 coins left the wall.
- 600 cancelled and 100 traded: the cancelled share is 600 / 700 = 86%, at least 70%, so the wall is pulled. The log reads "Wall at 99.95 pulled (likely spoof). 86% of the drop was cancellation".
- 300 cancelled and 400 traded: the cancelled share is 300 / 700 = 43%, so the wall is absorbed.
What each outcome does to your trade
Any of the four outcomes cancels a pending entry that rests in front of that wall. For an open trade, the reaction depends on the outcome. The details are on Protection, re-plans and exits.
| Outcome | Pending entry | Open trade |
|---|---|---|
| Pulled | Cancelled. A re-plan on the remaining walls may follow (replan_after_front_pull) | Re-anchor to a backup wall, hold in profit at breakeven, or exit at market (pulled_wall_exit) |
| Absorbed | Cancelled. On a stack of several walls, re-planned at once from the remaining walls (replan_on_stack_loss) | Never an exit. Re-anchor, or move the stop to breakeven when in enough profit (on_absorbed_after_fill) |
| Faded | Cancelled. A re-plan may follow, as for a pull | Kept, unless exit_on_wall_faded is on. Then it is handled like a pull |
| Broken | Cancelled. On a stack of several walls, re-planned at once, as for an absorbed wall | No action: the exchange stop handles it |
Pending entries are also cancelled after pending_timeout_s (300 s) without a fill. The bot counts pulled walls per coin. The scanner can use that count to skip coins that spoof a lot (max_spoof_rate; see the scanner).
The 4h support/resistance filter
A wall that lines up with a level where price turned before is more likely to matter. With sr_filter on (the default), Wallbot only trades a wall that sits at such a higher-timeframe level.
- Candles. It loads
sr_timeframecandles (default 4h) for the lastsr_lookback_days(30 days). Only fully closed candles count, so the filter never looks into the future. - Pivots. A pivot high is a candle whose high is above the highs of
sr_pivot_strength(2) candles on each side. A pivot low mirrors it. A pivot only exists once its right-hand candles have closed. - Levels. Pivots within the level tolerance of each other merge into one level, their average. By default the tolerance is
sr_tolerance_pct(0.3%). - Match. The wall's zone must lie within the same tolerance of a level (0.3% by default), or contain it. A support wall needs a level at or below the current price, and a resistance wall needs one at or above it.
Tolerance per coin. sr_tolerance_mode chooses how the tolerance is set. fixed_pct (default) uses sr_tolerance_pct for every coin. atr follows each coin's volatility: sr_tol_atr_mult (0.1) times ATR(14) of the level candles as a share of price, kept between sr_tol_min_pct (0.05%) and sr_tol_max_pct (0.5%). It changes only when a new candle closes, and falls back to sr_tolerance_pct without enough candles. The same value is used to merge pivots, to match walls and for the bands on the charts, which show it as "±x%".
A wall without a level is skipped with a reason such as "Skipped wall: no 4h level at or below price within 0.3% of the wall at 99.95-100". The matched level is stored with the trade and shown in the "Placed" log line.
For a wall stack (below), sr_stack_rule decides what must match. With any (default), the stack passes if any of its walls is at a level. With nearest, only the nearest wall counts.
Example
Illustrative numbers. Price is 101.00 and a support wall sits at 99.95 to 100.00. Two 4h pivot lows at 99.70 and 99.80 are within 0.3% of each other, so they merge into one level at 99.75. The gap from 99.75 to the wall's low edge is 0.20 / 99.75 = 0.20%, within 0.3%, and the level is below price. The wall passes.
Wall stacks
Walls often come in groups on one side of the book. With entry_anchor set to stack (default), Wallbot treats them as one defence line:
- The stack is the nearest confirmed wall plus every confirmed wall on the same side whose far edge is within
stack_max_span_pct(1.5%) of the nearest wall's near edge. - The entry goes in front of the nearest wall.
- The stop goes behind the farthest wall in the stack, and the leverage is chosen so liquidation is behind every wall.
- Only the nearest wall can start a trade. A confirmed wall farther out is never used on its own. If it is also outside the stack span, the log says why, for example "ENAUSDT support 0.23998-0.24011 not used: not the nearest wall (nearest 0.24388-0.24401), outside its stack span 1.5%".
With single_wall, the entry and stop sit around one wall only, as in older versions. A stack of one wall behaves the same in both modes.
Example
Illustrative numbers. Price is 101.00. Wall A (100.45 to 100.50) is the nearest. Wall B's far edge, 99.50, is (100.50 - 99.50) / 100.50 = 0.99% from A's near edge, inside the 1.5% span, so B joins. Wall C's far edge, 98.30, is 2.19% away, so it does not. With the default stop (0.5% behind the far edge), the stop is 99.50 x 0.995 = 99.0025, rounded away from the entry to 99.00. The entry is one tick in front of A, at 100.51.
Before the fill, a stack that loses a wall is re-planned. When any wall of a pending entry's stack fades, is pulled, absorbed or broken, the entry is cancelled (and the cancel confirmed) and planned again from the remaining walls with replan_on_stack_loss on (default, wall hug only): in front of the nearest wall, behind the farthest, at the highest leverage that passes every check. If the new plan is the same, the order stays; if it fails, the entry is only cancelled. A pulled or faded front wall waits replan_cooldown_s first (After the front wall is pulled).
After the fill, the stack keeps working. If stack walls disappear and the farthest remaining wall is closer to price, the stop can be tightened behind it (tighten_stop_on_stack_change). If the anchor wall is pulled, another wall of the stack can take over as the anchor. Both are explained on Protection, re-plans and exits.
Related pages
- Entries, stops and sizing: how a confirmed wall becomes an order.
- Protection, re-plans and exits: what happens while a trade is pending and open.
- Coins, movers and limits: which coins get wall tracking at all.
- Settings: Walls: every wall setting with its bounds.