Heatmap crypto controls: market, pair and auto setup for the pair

When the heatmap runs on a crypto source, a control row selects the market (Binance Spot, Binance USD-M Perp, Bybit Perp) and the pair, and the Rendering tab offers an Auto setup that derives the volume filter, noise floor, big-order threshold and visible price range from the live data of that pair.

Senzoukria · Documentation · Updated September 2026


Where to find it

Where
Heatmap (crypto source) → control row; Heatmap settings → Rendering tab → Auto setup for this pair → Tune
Default pair
BTCUSDT for each market; the last pair is remembered per market
Scope
Analysis only: crypto feeds are public market data, no order can be sent

What it does

The control row appears when the chart data source is a crypto feed. A Crypto market select lists Binance Spot, Binance USD-M Perp and Bybit Perp; the pair button opens the symbol picker for that market. The pair is stored per market, so switching Spot to Perp brings back the last pair used on Perp. Market identity is kept separate from the ticker because BTCUSDT exists on all three venues with different books.

Crypto quote precision is separated from the display grouping. The display step is the quote tick raised so that at least 0.1 % of the price fits in 160 rows, rounded to a 1 / 2 / 5 multiple; bids are grouped rounding down and asks rounding up, so the best bid and best ask never land on the same displayed row. The initial visible half-range is the larger of 40 steps and 0.05 % of the price.

Auto setup for this pair is a button in the Rendering tab of the settings. No vendor publishes per-pair thresholds, so the values are measured on the data currently in memory, at your click and never silently: trade sizes of the last 30 minutes of the ring (measured from the last trade, not the wall clock), the sizes of the last book snapshot, and the prices of the last 5 minutes.

Settings

What Tune writes, and the data it needs (pairAutoConfig.ts)
Setting writtenRuleRequires
Volume filter ≥ (Trades tab)98th percentile of recent trade sizes: the top 2 % of trades keep a bubbleAt least 200 trades in the last 30 minutes
Low floor (Rendering tab)40th percentile of the book sizes, rounded down to the quantity stepAt least 10 book levels
Big order threshold (DOM ladder)97th percentile of the book sizes, rounded up: the top 3 % of levelsAt least 10 book levels
Visible price rangeRange of the last 5 minutes × 0.75 on each side of the price, between 20 and 400 rowsAt least 20 prices in the last 5 minutes
Rounding step0.001 on crypto, 1 lot on futures

How to use it

  • Pick the market first, then the pair: the symbol picker filters on the selected venue.
  • Let the feed run a few minutes, open the settings, Rendering tab, and click Tune. The note under the button reports Tuned on {trades} trades and {levels} book levels, or Not enough live data yet when a rule lacks data.
  • Only the values that could be computed are written; a setting whose rule had too little data keeps its current value. The result is saved with the instrument's heatmap settings.
  • The viewport is moved to the computed range once; you can zoom again afterwards, Tune does not lock the scale.

Limits and pitfalls

  • Tune uses the live ring only, never the archived crypto history, so a chart opened seconds ago has nothing to measure.
  • The thresholds are quantiles of the recent past. A regime change (news, funding) makes them stale; click Tune again rather than expecting them to follow.
  • The button also exists on futures sources with the same rules, in contracts; the crypto specificity is the 0.001 rounding step.
  • Crypto sources are read-only market data: there is no account, no position and no order ticket on these heatmaps.

This page in other languages

Frequently asked questions

Why does Tune say there is not enough data?
Each rule has a floor: 200 trades in the last 30 minutes for the volume filter, 10 book levels for the floor and big-order threshold, 20 prices in the last 5 minutes for the range. On a quiet pair the trade rule is usually the one missing; the book rules still apply.
Does the display step change the data?
No. Grouping only decides which row a level is drawn on. Bids round down and asks round up so the spread stays visible; the venue precision is unchanged.
Is the pair shared with the crypto footprint?
The heatmap stores its pair per market in its own key. The footprint has its own selection; changing one does not change the other.

Keep reading