Wallbot

Coins, movers and limits

The scanner decides which coins get live order-book tracking. A set of limits decides how many trades may run at once, how many may lean the same way, and when new entries stop for the day.

The scanner

With scanner_enabled on (default), Wallbot ranks all USDT perpetuals every scan_interval_min (10 minutes). The best watch_count (5) coins become the core watch list. Only watched coins get wall tracking and can be traded. The idea is to pick liquid coins that are moving sideways, where walls tend to hold.

The scanner as a funnel: all USDT perpetuals, then hygiene rules and minimum volume, then the 40 largest by volume get indicators and filters, then the top 5 by score are watched and traded All USDT perpetuals on the exchange Hygiene rules and 24h volume of at least 50M USDT 40 largest by volume: 15m candles, trend, squeeze, funding, suitability Top 5 by score: watched Coins with an open or pending trade stay watched
Each scan narrows the market down to a short watch list. The numbers are the defaults.

The steps

  1. Hygiene rules, checked first, without fetching candles. A coin is excluded if it is on symbol_denylist, has a non-ASCII symbol (exclude_non_ascii_symbols), was listed fewer than min_listing_age_days (30) days ago, allows less than min_max_leverage (20x), or is missing from symbol_allowlist when that list is set.
  2. Volume. The 24h volume must be at least scan_min_volume_usd (50M USDT). Thin markets slip badly at high leverage.
  3. Indicators. The scan_max_candidates (40) largest coins by volume get 15-minute candles. A coin then fails if its trend strength (ADX) is above scan_max_adx (25), if its Bollinger width is in the lowest scan_min_bb_pctile (20) percentile (a squeeze, which often comes before a breakout), or if its funding rate is beyond scan_max_funding_pct (0.05%).
  4. Suitability and size, all off by default: max_spread_bps, max_tick_pct, min_depth_1pct_usd, min_atr_to_wall_band, max_spoof_rate (the share of the coin's confirmed walls that were pulled), max_smallest_position_usdt and affordability_filter.
  5. Score. Coins that pass get the score log10(24h volume) x scan_volume_weight (10) minus ADX x scan_adx_weight (1). prefer_near_4h_level adds near_level_boost (+10) for coins with a 4h level inside the wall distance band. It never excludes a coin.
  6. Watch list. The top watch_count by score are watched (at most 3 when MEXC order books are used, because they are polled). Coins with an open or pending trade always stay watched.

Example

Illustrative numbers. Coin A trades 200M USDT a day with an ADX of 18: score = 8.30 x 10 - 18 = 65.0. Coin B trades 1,000M USDT with an ADX of 24: score = 9.00 x 10 - 24 = 66.0. B ranks just above A. A coin C with an ADX of 31 fails as "trending (ADX 31)" and gets no score.

The dashboard's scanner table shows each coin's reason, such as "excluded: on the denylist" or "filtered: spread 12.3 bps (max 8)". Each scan logs its exclusions once. With the scanner off, the bot watches the coins in manual_symbols. Recording-only coins (record_watch_count) are never traded.

Movers and core coins

The top movers group is a paper experiment. With movers_enabled on, each scan also picks the movers_count (3) coins with the largest 24h price change, up or down.

Note. Fast-moving coins are exactly where trends break walls. Movers skip the trend filter on purpose, so their results can differ a lot from the core group. Compare the two groups in paper mode before you use movers with real money.

My coins (pinned coins)

Coins you pin in the dashboard's My coins panel (pinned_coins) are watched in addition to the core and movers lists, never instead of them. A pinned coin is never counted as core or as a mover.

Open-trade limits

Isolated margin keeps each trade's loss inside its own margin. But every trade's margin is still taken from your balance while it runs, so several trades add up.

The correlation guard

Crypto coins often move together. Three longs on BTC, ETH and SOL are close to one big bet. The guard limits this.

Example

Illustrative numbers. Longs are open on ETHUSDT and SOLUSDT. A new BTCUSDT support wall confirms. BTC's correlation is 0.91 with ETH and 0.86 with SOL, both above 0.8, so two correlated longs already run. That reaches the limit of 2 and the long is skipped: "Entry skipped by the correlation guard: 2 long trade(s) already on coins correlated above 0.8 (ETHUSDT 0.91, SOLUSDT 0.86); limit 2". A short on BTC would still be allowed.

Backtests replay one coin at a time, so the guard cannot fire there.

Both sides on one coin (Hedge Mode)

By default a coin holds at most one Wallbot trade. With allow_both_sides on and a Binance account in Hedge Mode, the bot may hold one long and one short on the same coin at once. Paper trading and backtests simulate Hedge Mode.

Nearest-side priority

Without both sides, a pending entry on one side blocks the other side of that coin. With nearest_side_priority on (off by default), a fully qualifying setup on the other side replaces the pending entry when its entry is at least side_switch_closer_pct (30%) closer to the price. The pending entry is cancelled and the cancel confirmed before the new one is placed. There is no switch when the pending entry is within side_switch_min_dist_pct (0.1%) of the price, never more than one per coin per side_switch_cooldown_s (60 s), and never once the entry has filled. The pending entry being replaced does not count against max_positions or the other limits. Details: Switching to the closer side.

Daily loss limit and live safety caps

daily_loss_limit_pct (10%) applies in every mode. Once today's realised loss reaches this share of the day's starting balance, new entries pause and every pending entry is cancelled. Open positions keep their stops. The pause lifts at the next UTC day, when you press "Resume entries", or when you press "Reset today's loss count" on the Live learning page (daily_loss_reset_button). The reset starts today's count again from zero for both the daily loss limit and the live safety daily cap, and in live mode needs the typed confirmation "I ACCEPT". See Reset today's loss count.

Example

Illustrative numbers. The day starts with 500 USDT, so the limit is 50 USDT. After losses that add up to -50.00 USDT, the log reads "Daily loss limit reached (-50.00 USDT). New entries are paused until tomorrow or until you resume."

In live mode, and in testnet when safety_in_testnet is on, the live safety caps add fixed USDT limits that cannot be switched off. They are safety_total_loss_usdt, safety_daily_loss_usdt and the sizing cap safety_balance_cap_usdt. In live mode, raising these limits, max_positions, the correlation limit or switching on movers or both sides needs the typed confirmation "I ACCEPT". Realized loss in all these limits includes funding fees, and in live and testnet uses Binance's values when the close check corrected a trade. See Safety for the details.

Warning. Loss limits only stop new entries. They cannot undo a loss that has already happened, and a gap past a stop can lose more than planned. Keep the caps small while you learn how the bot behaves.

The gates in front of every entry

Before a confirmed wall is even planned (see Entries, stops and sizing), it must pass these portfolio gates, in this order:

  1. No lost Wallbot order is being cleaned up on that coin.
  2. The coin and side are free (one trade per side; the other side only with both sides allowed, or by a side switch).
  3. No front-wall re-plan is waiting on that coin and side (After the front wall is pulled).
  4. Fewer than max_positions trades are open or pending.
  5. For a mover, a movers slot is free.
  6. No live safety loss cap is reached.
  7. The correlation guard allows it.
  8. In testnet and live: the user-data stream is connected and reconciled, the key guard is not engaged (after a -2015 or a burst of -1021, until signed requests are clean for key_stable_minutes, 10), and Binance is not rate-limiting the bot (HTTP 429 back-off or a 418 ban).

Entries are also paused while the daily loss limit is hit, after "Pause entries" or "Prepare to stop", and while the bot shuts down.