mrD-Indicators

Most introductions to the liquidation heatmap teach it as a magnet: price drifts toward clustered liquidity, taps it, and reverses — so you fade the tap. That framing is not wrong, but it is incomplete, and for the trader trying to ride a multi-week wave, it is frequently the less profitable half of the picture. This guide takes the other half seriously. We treat liquidation clusters as fuel for the prevailing trend rather than as static support and resistance, and we pair them with RSI — read as a momentum-regime instrument — to define and ride long-term waves.
The division of labour is the whole idea: RSI tells you which wave you are in (the regime and its direction), and the liquidation heatmap tells you where the fuel is that will drive the next impulsive leg of that wave. One supplies the bias; the other supplies the target and the accelerant.
This matters across the whole market, not just majors. The mrD liquidation heatmap covers 500+ perpetual pairs on Binance, so the read scales to the entire altcoin board — and altcoins, with higher effective leverage and thinner books, tend to produce the largest cascades relative to size, which is exactly what powers a clean long-term wave.
The tone here is study-led: we define terms precisely, explain why the mechanism works the way it does, cite the relevant literature, and only then translate it into entries and invalidations. The goal is a reader who can both pass an exam on liquidation dynamics and place a disciplined swing trade with the tool.
What a liquidation heatmap actually is
A liquidation heatmap is a model-based estimate of where leveraged positions are most likely to be force-closed, plotted on the same time and price axes as the candlesticks. Bright clusters mark price levels with a high estimated concentration of liquidation-prone positions; dark areas mark levels with little.
Two words in that definition do all the work, and most beginners skip them:
Model-based. Exchanges do not publish a list of every trader's liquidation price. A heatmap infers the distribution from public market data and a set of assumptions about how leverage is typically used. Different tools make different assumptions, so two liquidation heatmaps of the same market can disagree. Treat any single heatmap as one estimate, not as the order book.Estimate. Because it is inferred, a cluster is a probability density, not a confirmed pile of stop orders. The correct mental model is a weather forecast: directionally useful, occasionally wrong, never to be confused with the sky itself.
We deliberately do not describe the internal formula that produces the clusters — the leverage assumptions, weighting, and decay are implementation details, and the trading edge does not depend on knowing them. What matters for trading is the behaviour of the levels the heatmap surfaces, and that behaviour follows directly from market microstructure, which we can reason about in the open.
Coverage: 500+ Binance altcoin pairs
A liquidation heatmap is only useful for swing trading if you can run it on the markets that actually trend. The mrD liquidation heatmap is computed for 500+ Binance perpetual pairs — not just BTC and ETH but the long tail of altcoins where the cleanest multi-week waves tend to appear.
Two reasons altcoins matter more here than majors:
Higher effective leverage. Altcoin perp traders run more leverage on average, so their liquidation prices sit closer together, and the clusters are denser relative to the coin's open interest. More crowding means more fuel.Thinner books. With less resting liquidity to absorb forced market orders, an altcoin cascade moves the price further per dollar liquidated. The same cluster that nudges BTC can launch an altcoin's next impulsive leg.
Because the read is identical across every pair, you can scan the whole board for the same setup — a strong RSI regime plus a well-stocked cluster in the trend direction — and trade wherever it lines up best, instead of forcing the major to cooperate.
The mechanism: a liquidation is a market order
This is the single most important sentence in the article, so it gets its own section.
When a leveraged position is force-liquidated, the exchange's liquidation engine does not politely ask for a fill. It submits a market order to close the position. A liquidated long is closed by selling into the book; a liquidated short is closed by buying from the book. The order is price-insensitive — it must execute — so it consumes resting liquidity and pushes the price further in the direction that caused the liquidation.
That asymmetry is the whole game:
A cluster of long liquidations below the price is latent selling pressure. If the price reaches it, forced selling accelerates the move down.A cluster of short liquidations above the price is latent buying pressure. If the price reaches it, forced buying accelerates the move up — the classic short squeeze.
So a liquidation cluster is not a wall that price bounces off. It is a tank of pre-committed, direction-locked market orders that fires in the direction the price is already travelling when it arrives. That is why, in an established trend, the cluster ahead of price is best read as an accelerant, not a barrier.
Reflexivity and the deleveraging spiral
The mechanism compounds. Each liquidation pushes the price toward the next cluster, which triggers more liquidations, which push the price further still. This positive feedback loop is the liquidation cascade, and it is a textbook example of a self-reinforcing, or reflexive, process.
The academic spine here is well established. Brunnermeier and Pedersen's "Market Liquidity and Funding Liquidity" (Review of Financial Studies, 2009) formalises the margin spiral: falling prices raise margin requirements, forcing deleveraging, which lowers prices further. Shleifer and Vishny's work on fire sales (Journal of Finance, 1992; and "The Limits of Arbitrage", 1997) describes the same dynamic from the asset-pricing side — forced sellers meet a thin pool of buyers and prices overshoot fundamentals. George Soros's notion of reflexivity (The Alchemy of Finance, 1987) is the conceptual umbrella: market prices and the conditions that drive them feed back on each other rather than moving independently.
Crypto perpetual futures are arguably the purest live laboratory for these ideas, because leverage is high, liquidation is automatic, and the resulting flow is observable. An empirical literature has grown around it — for example, Qin, Zhou, and Gervais's "An Empirical Study of DeFi Liquidations" (IMC 2021) documents cascade dynamics in on-chain lending, and the same shape recurs in centralised perpetual markets.
Evidence: cascades are real and large
The historical record is unambiguous that liquidation flow can dominate price over short windows:
12 March 2020 ("Black Thursday"). A COVID-driven selloff triggered a deleveraging cascade across crypto derivatives; widely reported that BitMEX alone saw roughly a billion dollars of liquidations, and a brief exchange outage is often credited with interrupting the spiral before it ran further.19 May 2021. A single-day crash produced an estimated ~$8 billion in liquidations across exchanges according to liquidation aggregators — one of the largest forced-deleveraging days on record, with the bulk on the long side fuelling the drop.June 2022. The unwind of large leveraged funds and lenders produced sustained, multi-day forced selling as positions were liquidated into a falling market.
Exact figures vary by aggregator and methodology (another reminder that liquidation data is estimated), but the direction of every one of these episodes is consistent with the mechanism above: forced flow pushed price further in the direction it was already going. That is the empirical case for trading with the cascade rather than in front of it.
Two schools, and why continuation wins the wave
There are two coherent ways to use a liquidation heatmap. Both are valid; they apply at different moments.
The magnet/reversal school says price is drawn toward clustered liquidity, taps it, and reverses — so you fade the tap and treat the cluster as support/resistance. The grain of truth: market makers and aggressive participants do often push price into obvious liquidity to harvest it, and a reversal can follow once the fuel is spent.
The cascade/continuation school says the cluster is fuel for the existing trend, so the higher-expectancy play is to position for the acceleration through the cluster, in the trend direction.
Here is the reconciliation, and the reason this guide leans hard on continuation:
A liquidation cluster reverses price only after its fuel is consumed. On the way in, the dominant effect is acceleration. The reversal — if it comes — happens on the way out, once the forced flow is exhausted and no fresh aggressor remains.
So the reversal trade is a late, exhaustion-dependent trade: you are betting the tank is now empty. The continuation trade is an early, mechanism-aligned trade: you are betting the tank is about to fire. For a long-term wave, where you have neither the desire nor the ability to time every exhaustion precisely, aligning with the mechanism is the more repeatable edge. The reversal is the specialist's trade for the end of a wave; continuation is the workhorse for the body of one.
Pairing the heatmap with RSI for long-term waves
The liquidation heatmap has one blind spot: it never tells you which way the wave is running. It shows where forced fuel sits; it is silent on direction. That is precisely the gap RSI fills, and why the two are complementary rather than redundant.
We use RSI exactly as the companion guide develops it — as a momentum-regime instrument, not an overbought/oversold trigger. Three properties do the work (full treatment in RSI as a Momentum Instrument):
Regime (Cardwell range rules). In a bull wave, RSI oscillates roughly in the 40–80 band and uses 40–50 as support; in a bear wave, it lives in 20–60 and uses 50–60 as resistance. The range RSI occupies defines the wave. This is your bias — the same job Step 1 needs to be done.The 50-line. Holding above 50 confirms the bull regime; holding below 50 confirms the bear regime. A decisive, sustained cross of 50 on the higher timeframe is the earliest sign a wave is changing — and a reason to stand down until the new regime is clear.Divergence. Price making a new wave extreme while RSI does not is the classic exhaustion tell. Read at the moment price reaches a fuel cluster, an RSI divergence is the signal that the cascade is spending its last fuel — your cue to take profit, not to add.
The mapping onto the framework is clean: RSI regime = direction (Step 1), liquidation cluster = target/fuel (Step 2), RSI pullback into range support = entry timing (Step 3), RSI divergence at the cluster = exhaustion exit (Step 4). Read the heatmap and RSI together, and each step has an owner.
Because RSI is timeframe-relative, run it multi-timeframe: the weekly/daily RSI sets the wave regime (bias), the 4h RSI times the pullback entry. A long is only valid when the daily regime is bullish, and the 4h has pulled back into its 40–50 support and is turning up.
The trend-following framework
Four steps. Each step is a filter; if a step fails, there is no trade.
Step 1 — Establish the wave with RSI (bias)
The heatmap tells you where forced flow waits, never which way the market wants to go. You supply direction from the RSI regime plus structure, on the higher timeframe:
Bull wave — daily/weekly RSI in the 40–80 band, holding above 50, respecting 40–50 as support; price printing higher highs and higher lows. → long bias.Bear wave — daily/weekly RSI in the 20–60 band, holding below 50, rejecting from 50–60 resistance; lower highs and lower lows. → short bias.Range/regime in flux — RSI crossing 50 freely, reaching both extremes, no respected boundary → no bias, no trade. In a range, clusters revert to magnet/reversal behaviour — a different playbook.
Run it multi-timeframe: the weekly/daily RSI sets the wave (bias); the 4h RSI is reserved for timing in Step 3. Match the structure timeframe to your hold — for long-term waves, that means a daily (or weekly) regime, held for weeks.
Step 2 — Locate the fuel cluster in the trend direction
With a long bias, your interest is the nearest dense short-liquidation cluster above price — that is, the buy fuel. With a short bias, the nearest dense long-liquidation cluster below the price — the sell fuel.
Quality of the cluster matters:
Density — brighter and broader is more fuel.Distance — close enough that price can realistically reach it within your trade horizon, far enough that there is room to enter before the move.Isolation — a cluster with a thin "gap" between current price and the cluster tends to produce a cleaner, faster run, because there is little intervening liquidity to slow the approach (the same logic as a liquidity vacuum on the depth heatmap).
Pairing the heatmap with RSI for long-term waves
The liquidation heatmap has one blind spot: it never tells you which way the wave is running. It shows where forced fuel sits; it is silent on direction. That is precisely the gap RSI fills, and why the two are complementary rather than redundant.
We use RSI exactly as the companion guide develops it — as a momentum-regime instrument, not an overbought/oversold trigger. Three properties do the work (full treatment in RSI as a Momentum Instrument):
Regime (Cardwell range rules). In a bull wave, RSI oscillates roughly in the 40–80 band and uses 40–50 as support; in a bear wave, it lives in 20–60 and uses 50–60 as resistance. The range RSI occupies defines the wave. This is your bias — the same job Step 1 needs to be done.The 50-line. Holding above 50 confirms the bull regime; holding below 50 confirms the bear regime. A decisive, sustained cross of 50 on the higher timeframe is the earliest sign a wave is changing — and a reason to stand down until the new regime is clear.Divergence. Price making a new wave extreme while RSI does not is the classic exhaustion tell. Read at the moment price reaches a fuel cluster, an RSI divergence is the signal that the cascade is spending its last fuel — your cue to take profit, not to add.
The mapping onto the framework is clean: RSI regime = direction (Step 1), liquidation cluster = target/fuel (Step 2), RSI pullback into range support = entry timing (Step 3), RSI divergence at the cluster = exhaustion exit (Step 4). Read the heatmap and RSI together, and each step has an owner.
Because RSI is timeframe-relative, run it multi-timeframe: the weekly/daily RSI sets the wave regime (bias), the 4h RSI times the pullback entry. A long is only valid when the daily regime is bullish, and the 4h has pulled back into its 40–50 support and is turning up.
The trend-following framework
Four steps. Each step is a filter; if a step fails, there is no trade.
Step 1 — Establish the wave with RSI (bias)
The heatmap tells you where forced flow waits, never which way the market wants to go. You supply direction from the RSI regime plus structure, on the higher timeframe:
Bull wave — daily/weekly RSI in the 40–80 band, holding above 50, respecting 40–50 as support; price printing higher highs and higher lows. → long bias.Bear wave — daily/weekly RSI in the 20–60 band, holding below 50, rejecting from 50–60 resistance; lower highs and lower lows. → short bias.Range/regime in flux — RSI crossing 50 freely, reaching both extremes, no respected boundary → no bias, no trade. In a range, clusters revert to magnet/reversal behaviour — a different playbook.
Run it multi-timeframe: the weekly/daily RSI sets the wave (bias); the 4h RSI is reserved for timing in Step 3. Match the structure timeframe to your hold — for long-term waves, that means a daily (or weekly) regime, held for weeks.
Step 2 — Locate the fuel cluster in the trend direction
With a long bias, your interest is the nearest dense short-liquidation cluster above price — that is, the buy fuel. With a short bias, the nearest dense long-liquidation cluster below the price — the sell fuel.
Quality of the cluster matters:
Density — brighter and broader is more fuel.Distance — close enough that price can realistically reach it within your trade horizon, far enough that there is room to enter before the move.Isolation — a cluster with a thin "gap" between current price and the cluster tends to produce a cleaner, faster run, because there is little intervening liquidity to slow the approach (the same logic as a liquidity vacuum on the depth heatmap).
Step 3 — Time the entry with an RSI pullback
Do not enter the heatmap alone, and do not chase an extended wave. The cluster is a region of interest; the trigger is an RSI pullback into range support, resuming in the trend direction:
Long: wait for the 4h RSI to pull back into its 40–50 support zone without losing 50 on the higher timeframe, then turn back up. That is the dip inside an intact bull wave — the lowest-risk point to position for the run into the cluster above.Short: wait for the 4h RSI to rally into its 50–60 resistance zone and roll back over, with the higher-timeframe regime still below 50.The ideal sequence is: daily regime intact → 4h RSI pulls into range support → RSI turns back with the wave → enter, with the fuel cluster sitting ahead in the trend direction. You are buying the pullback inside the wave, not chasing the cluster.
This is deliberately not an order-flow trigger. Open interest, CVD, and footprint timing are powerful but belong to the companion order-flow guide; for long-term waves, the RSI pullback is the cleaner, slower, more robust trigger.
Step 4 — Targets, invalidation, and the RSI-divergence exit
The thesis is "price reaches the cluster and accelerates." It is wrong the moment the wave structure breaks or the RSI flips regime.
Stop: beyond the last structural swing against your trade (the swing low for a long, swing high for a short) — and additionally, treat a decisive higher-timeframe RSI cross of the 50-line against you as a regime-failure exit. If the wave itself is over, the fuel thesis is void.Targets: the far edge of the fuel cluster for the first scale, then the next cluster in the trend direction. Cascades chain one cluster to the next; partial profit at the first, runner toward the second, trail behind a higher-timeframe structure.Exhaustion exit (the RSI divergence). When price reaches the far side of a cluster, and RSI prints a divergence — a new price extreme not confirmed by a new RSI extreme — the cascade is spending its last fuel. Take profit on the runner. That divergence is, not coincidentally, the entry signal for the reversal specialist — but for you, it is the exit, not a reason to flip.
Two repeatable setups
Concrete, trend-only, RSI-timed, built for multi-week holds.
Set up A — Long-liquidation continuation (short swing)
Context: daily RSI in a confirmed bear regime (20–60 band, holding below 50, rejecting from 50–60 resistance); price in lower highs / lower lows.
Map: a dense long-liquidation cluster sits below price on the daily heatmap with a relatively thin approach.
Trigger: the 4h RSI rallies into its 50–60 resistance zone — without the daily reclaiming 50 — and rolls back over.
Plan:
Entry: on the 4h RSI roll-over out of resistance, above the cluster.Stop: above the structural swing high that formed the lower high; abandon if the daily RSI reclaims 50 decisively.Target 1: far edge of the long-liquidation cluster (the cascade tends to overshoot it).Target 2: next long-liquidation cluster below.Manage: trail behind daily structure; exit the runner when RSI prints a bullish divergence as price reaches the cluster.
Set up B — Squeeze continuation (long swing)
Mirror of A. Context: daily RSI in a bull regime (40–80 band, above 50, respecting 40–50 support). Map: dense short-liquidation cluster above price on the daily heatmap, thin approach. Trigger: 4h RSI pulls back into its 40–50 support and turns up while the daily holds above 50. Plan: long on the RSI turn-up, stop below the structural swing low (and on a decisive daily RSI loss of 50), target the far edge of the cluster, then the next cluster above, exit the runner on a bearish RSI divergence at the cluster.
Both setups share the same skeleton because they share the same engine: RSI defines the wave, the heatmap marks the fuel, you enter on the RSI pullback in the trend direction, and you step aside when RSI diverges, and the fuel is spent.
Confluence that raises conviction
For long-term waves, two confirmations sit naturally on top of the RSI-plus-heatmap core.
RSI multi-timeframe alignment (primary). The strongest swings occur when the weekly and daily RSI agree on the regime and the 4h pullback fires in the same direction. Three timeframes of RSI pointing the same way, into a well-stocked cluster, is the high-conviction wave. A single-timeframe RSI read is tradeable only with reduced size.Funding rate. Persistently positive funding means crowded longs — the long-liquidation clusters below are better-stocked, and more dangerous once a bear wave starts. Persistently negative funding means crowded shorts — the short-liquidation clusters above are the fuel for a squeeze. Funding tells you which side of the heatmap is loaded, which complements RSI, telling you which way the wave runs.
The remaining order-flow confirmations — open interest, CVD, and orderbook depth — are deliberately out of scope here. They reward a faster, intraday read and get their own treatment in the companion order-flow heatmap guide. For a multi-week wave, RSI regime plus a loaded cluster plus aligned funding is already a complete, robust thesis.
Common mistakes
Treating clusters as fixed support/resistance. The heatmap is dynamic — clusters build, drain, and shift as positions open and close. A level that was loaded an hour ago may be empty now. Re-read it; do not anchor to a stale screenshot.
Fading into a cascade. Standing in front of a triggering cluster to catch the reversal is the most expensive beginner error. The reversal comes after exhaustion, not on the way in. Until RSI actually diverges, you are leaning against forced market orders.
Forgetting it is an estimate. Because the clusters are inferred, sometimes the fuel simply is not there, and price stalls at a bright band for no visible reason. Your invalidation (Step 4) exists precisely for this — the model can be wrong, you cannot care.
Trading clusters in a range. The framework is wave-only. When RSI crosses 50 freely and reaches both extremes, there is no regime, no dominant direction for the fuel to accelerate, and the magnet/reversal behaviour reasserts itself. Demanding a clear RSI regime in Step 1 is not optional.
Chasing instead of waiting for the RSI pullback. Entering as price is already running into the cluster, rather than on the RSI pullback that precedes the run, ruins the risk-reward. The edge is buying the dip inside the wave (RSI into range support), not chasing the impulse.
Ignoring funding. Without it, you are reading where fuel might be, but not whether the crowd is loaded on that side. A short-liquidation cluster above price means far more when funding is deeply negative (crowded shorts) than when it is flat.
A pre-trade checklist
Run it before every entry. Any "no" is a pass.
Is the daily/weekly RSI in a clear regime (bull 40–80 above 50, or bear 20–60 below 50) — not crossing 50 freely?Is the fuel cluster in the wave direction (shorts above for longs, longs below for shorts)?Is the approach to the cluster reasonably thin (room to run)?Did the 4h RSI pull back into range support and turn in the wave direction (the entry trigger)?Does funding confirm the loaded side (negative for a squeeze long, positive for a long-liq short)?Is the invalidation a real swing level before the cluster, plus a higher-timeframe RSI 50-cross failsafe?Is risk-to-reward at least 2:1 to the far edge of the cluster, after fees?Is the position size within your per-trade risk limit?
All yes — execute. And the moment RSI diverges at the cluster, the continuation trade is done.
References and further reading
Brunnermeier, M. K. & Pedersen, L. H. (2009). Market Liquidity and Funding Liquidity. Review of Financial Studies, 22(6) — the margin/funding spiral.Shleifer, A. & Vishny, R. W. (1992). Liquidation Values and Debt Capacity: A Market Equilibrium Approach. Journal of Finance, 47(4); and (1997) The Limits of Arbitrage. Journal of Finance, 52(1) — fire-sale dynamics.Soros, G. (1987). The Alchemy of Finance — reflexivity as a market principle.Qin, K., Zhou, L., Gervais, A. et al. (2021). An Empirical Study of DeFi Liquidations. ACM Internet Measurement Conference — cascade dynamics in leveraged markets.Liquidation aggregators (e.g., Coinglass, Coinalyze) for the historical episode figures cited above; note that estimates differ across providers.
This article is educational, not financial advice. The liquidation heatmap is an estimate, not a record of real orders. Trading involves risk; never risk capital you cannot afford to lose.

There are over a thousand actively traded perpetual pairs on Binance Futures. No human can scan all of them by hand and still execute on time. MRD Indicators exists to solve exactly that — surface the handful of coins printing a setup right now, so you spend your attention on entries, not on hunting.
What MRD Indicators are — and what it isn't
MRD Indicators is a trend and signal discovery layer for crypto markets. It is not a charting platform, and it is not trying to be one.
Every quarter, a new startup launches with marketing copy claiming to "replace TradingView" or be "the next Sierra Chart" or "the Bookmap alternative". Those platforms have ten-plus years of charting maturity behind them — instrument coverage, drawing tools, replay, scripting, backtesting, broker integrations, edge cases nobody else has hit yet. Building a credible alternative is a decade of work, not a weekend repaint of a candlestick library. MRD Indicators is not in that race. We respect the lane and stay out of it.
We picked a different lane — the one most chart-first products treat as an afterthought. A traditional chart UI asks "which pair do you want to see?" and waits for an answer. MRD Indicators flips the question: across the universe of Binance pairs, which ones are setting up right now? Then it surfaces them, sorted, ranked, filtered — and only then do you open the chart.
Whatever charting tool you already trust, keep using it. MRD Indicators sits on top of your existing workflow, not in front of it. Bring the candidates' MRD surfaces to your usual chart setup, or stay inside MRD and confirm on the built-in chart. Either way works. The product's job is discovery.
The trend and signal scanner — the core of the product
The platform continuously evaluates the entire Binance Futures and Binance Spot universe across multiple timeframes. Every kline close, the scanners refresh, and you see:
– Which pairs are in a confirmed uptrend right now
– Which pairs just printed an RSI extreme that historically reverts
– Which pairs are forming a divergence between price and volume
– Which pairs broke key support or resistance on real volume
– Which pairs are pressing into high-volume nodes
– Which pairs are seeing whale-sized accumulation or distribution
You filter by timeframe, exchange, signal type, minimum signal strength, 24h volume, market cap, and more. The list is live — it re-sorts as the next bar closes. One cohesive view of what is actually happening across the market, instead of clicking through one hundred charts one by one.
The built-in scanners cover the patterns most crypto traders care about: MRD Pullback, MRD Wave, MRD Divergence, MRD Trend, RSI Heatmap, AltScreener, Whales Screener, and Live Monitor. Each scanner runs in real time across the full Binance universe, and you can stack filters to narrow the result down to two or three pairs worth a chart open.
The logic behind every scanner is open and inspectable. RSI extreme means RSI extreme — with a visible threshold and a filter you control. If a built-in scanner does not match exactly what you trade, you author your own in DeltaDSL — the platform's scripting language — and your custom signal joins the screening layer the same way the native ones do. The new DeltaDSL Language Support extension for Cursor and VSCode brings hover docs, smart autocomplete, and signature help to that authoring workflow.
Charting is here — as a confirmation surface, not the product
When a scanner surfaces a candidate, you can open it on the chart immediately. The chart engine has what a serious crypto trader expects:
– Real-time candles and tick streams from Binance
– Standard indicator library: RSI, MACD, EMA, Bollinger, ATR, Stochastic, CCI, OBV, MFI, and more
– Orderflow stack: footprint candles, volume profile, anchored VWAP, depth heatmap, DOM ladder, liquidation matrix, large-trade markers, CVD
– Multi-pane layouts, multi-symbol grid, drawing tools, alerts
– Custom indicators authored in DeltaDSL
This chart is here so you can confirm the signal the scanner surfaced without leaving the tab. It is not marketed as a TradingView replacement, a Sierra Chart competitor, or a Bookmap alternative. It is not pretending to be the place where you do your full charting. If you prefer to confirm on a different platform, take the symbol over there. MRD's contribution to the workflow is the pair you should be looking at right now — not the act of looking at it.
Orderflow — context the candle alone cannot give you
Above the candle layer sits a full orderflow engine. Footprint candles show bid versus ask volume at every price level inside every bar. The depth heatmap reveals where resting liquidity is sitting in the order book over time. The DOM ladder streams real-time book depth. Large trades and liquidations are tagged on the chart as they print.
These are not decorations. They tell you whether the move the scanner caught is being absorbed or being chased, whether liquidity is thinning or thickening, and whether the trend has fuel left. Combining the scanner's "where to look" with orderflow's "what is actually happening there" is the core workflow MRD Indicators is built around.
From signal to live trade — autotrade on Binance
When a setup is worth taking, you do not have to leave the platform. The autotrade engine wires alerts directly to the official Binance API.
You pre-configure the rule once: position size, leverage tier, take-profit, stop-loss, partial fills, and max concurrent positions. Wire your scanner signal or your DeltaDSL alertcondition into it, and the next time it triggers, the order is submitted to Binance Futures or Binance Spot without a human in the loop.
API keys are stored encrypted in the browser and never sent to our servers. Orders open natively in your Binance account through the official API — same UI, same fee schedule, same liquidity. Autotrade is opt-in per rule, fully inspectable, and every trigger is logged.
Who the MRD Indicators are for
MRD Indicators is built for crypto traders who:
– Trade Binance Futures or Binance Spot
– Watch more than twenty pairs at a time and feel the cost of context-switching
– Want one place that finds setups across the full Binance universe in real time
– Prefer to see the logic behind every signal and decide for themselves what to take
The platform sits alongside whatever charting tool you already use, not in front of it. Its single job is to point you at the pairs that matter, the moment they start to matter. What you do with that pointer — chart it inside MRD, chart it on your usual platform, execute via autotrade, execute manually — stays your choice.
The shift
Stop scanning hundreds of coins by hand. Let the platform do the discovery part, and spend your attention on entries, on size, on risk — the parts of trading that actually compound.
#Binance #BinanceFutures #BinanceSquare #BNB #BTCUSDT #ETHUSDT #SOLUSDT #CryptoTrading #CryptoSignals #TrendTrading #Orderflow #AlgorithmicTrading #MRDIndicators #DeltaDSL

Write a script. Drop it into the MRD Indicators chart terminal. Watch it render on your live BTCUSDT chart and fire trades on Binance Futures the moment your signal triggers. The new DeltaDSL Language Support extension brings hover docs, autocomplete, and signature help to Cursor and VSCode for traders who prefer authoring outside the browser. MRD Indicators (app.mrd-indicators.com) is a trading terminal built around three pieces: a real-time chart engine, a custom-script runtime called DeltaDSL, and an autotrade bridge to Binance Futures and Binance Spot. The three pieces work as one round-trip: your script renders on the chart in real time, and every alertcondition you declare can push a live order through the official Binance API.
How DeltaDSL fits in
A DeltaDSL script is not a standalone program you run. It is embedded into the MRD Indicators chart, just like any built-in indicator. The chart engine streams OHLCV into your script every bar, your script computes values and emits draw calls, and the chart renders the result alongside RSI, MACD, volume profile, and everything else native to the terminal. The full lifecycle of one script:
Author — write the script. You can edit directly in the built-in Custom Script editor inside the MRD Indicators terminal, or — new today — in Cursor / VSCode with the DeltaDSL Language Support extension installed.Embed — save the script. MRD Indicators registers it as an indicator, and you toggle it onto any chart from the indicator panel.Render — the chart engine runs your script on every kline close (and optionally every tick), drawing your lines, bands, markers, and labels directly on the candles.Signal — your alertcondition(...) lines fire when their condition turns true. The terminal surfaces the alert in the alerts panel and forwards it to the autotrade engine.Execute — autotrade submits a market or limit order to your Binance account through the Binance API, sized according to the rules you pre-configured. The order shows up in your Binance Futures positions panel within milliseconds. There is no copy-paste between platforms, no webhook glue, no third-party automation service. The chart that draws your script and the engine that places your order are part of the same product.What the new Cursor / VSCode extension does Until today, every line of DeltaDSL was authored inside the browser textarea of the Custom Script editor. That works for short scripts. For longer strategies — multi-file refactors, git-tracked iterations, team review — a real IDE matters.
DeltaDSL Language Support is live on the Open VSX Marketplace. Install it in Cursor or VSCode, and every .dsl and .mrd file gets:
Syntax highlighting with the full keyword and built-in setHover documentation — point at any built-in, see its signature, kind, and short descriptionSmart autocomplete — Ctrl+Space suggests every built-in from the runtime catalog, plus your own variables and @input declarationsSignature help — typing fn( opens a parameter popup that highlights the active argument as commas advance25+ snippets for common patterns: header, plotLine, alertcondition, pane-osc, labelNew You author in Cursor / VSCode, paste the final script into the
Custom Script editor in MRD Indicators, and the same script runs live on the chart.
The 257-entry runtime catalog
Every hover tooltip and completion item is backed by a catalog generated directly from the runtime source. Every function in the extension is a function that actually exists on the platform, with the same signature. Docs cannot drift from reality. Coverage today:
Math — abs, pow, sqrt, clamp, lerp, iff, nzMoving averages — sma, ema, wma, vwap, vwap_anchoredOscillators — rsi, stoch, macd_hist, cci, mfiVolatility — atr, stdev, bbwidth, keltner_upperVolume + flow — obv, cmf, vp_high_volume_node, cvdMarket structure — pivothigh, pivotlow, crossover, crossunderMulti-timeframe — htf_resample, htf_alignDrawing primitives — plotLine, plotBand, labelNew, markerUpAlert wiring — alertcondition, with {{symbol}} / {{close}} placeholdersTyped inputs — input.int, input.float, input.color, input.source