A stop-loss feels like a promise. You set a price, the system watches for it, and your position closes before the damage spreads. Every part of that sentence is true except the guarantee, and the gap between "watches for it" and "closes it" is where accounts die.
Three different prices are involved. None of them is the one most traders assume.
A stop-loss is a conditional order, not a risk limit
The order sits in a conditional queue until a price condition is met. Meeting the condition does not close anything. It releases an order into the book, and that order then has to find a counterparty at some price.
Between the condition and the fill there are at least four failure points: the condition may be evaluated on a different price feed than the one that triggers liquidation, the released order may not fill, the fill may be far from the trigger, and the whole pipeline may be slower than the price move.
Three prices, three jobs
The mechanics separate cleanly once you name them.
The last traded price is the most recent print on that venue. It is fast, noisy, and thin books make it jump.
The mark price is a reference price the platform computes to assess position risk and calculate unrealized PnL. Its construction is venue-specific, and it is what liquidation logic generally watches.
The fill price is whatever the book pays when your order actually executes.
A stop-loss is usually evaluated against the first. Liquidation is usually evaluated against the second. Your exit executes at the third. Three different series, three different moments, one position.
What the exchange documentation says outright
This is not a subtle implementation detail. One exchange's Academy guide states it directly:
"The stop-loss is triggered by the last traded price, while liquidation is based on the mark price. Liquidation occurs before the stop-loss is triggered."
That single sentence explains a class of support tickets. You set a stop 2 percent away, the mark moved 2 percent first, and the liquidation engine reached the margin boundary before the conditional order ever became eligible.
The same guide lists the adjacent failure modes in the same language: an order triggered but not filled because no counterparty appeared or slippage was severe, price and liquidity gaps past the trigger level, cascading liquidations when many conditional orders fire together, and matching engine delays or API rate limits.
Triggered and still open
The second failure is structural rather than adversarial. A stop-limit order that fires into a falling book can sit unfilled at a price nobody wants. A stop-market order fills, but at whatever the book offers.
If your intent is exit, a limit price inside a stop is a decision to prefer a bad outcome over an uncertain one. That is a legitimate choice, but it is not the same as protection.
There is also a queue position problem. When thousands of conditional orders fire on the same tick, they are not all first in line. Some fill well, some fill late, and the ones that fill late fill worse.
Latency is a measurable term, not a vibe
Recent quantitative work treats the delay explicitly. A 2026 paper in Forecasting models liquidation as a first-passage problem where the executable price is observed through a delayed or smoothed mark, funding drains collateral continuously, and liquidation fires when the isolated margin surplus hits its maintenance boundary.
Two results are useful to anyone building or auditing this kind of system. Under a fixed observation delay, expected overshoot scales with the square root of that delay, and the probability of bad debt is governed by a latency-to-margin ratio.
Their published 60 minute boundary-breach probabilities for a ten times position are 1.7 percent on BTC, 4.1 percent on ETH and 13.5 percent on SOL. Those numbers move higher when the mark is time-weighted rather than instantaneous.
Read that as an engineering statement: a smoother mark reduces noise and increases the loss conditional on detection. Both choices are defensible. Neither is free.
Cascades are subcritical more often than the narrative suggests
The other 2026 study measures an actual cascade in flight, using the on-chain fill log of a transparent venue during the October 2025 event. Its branching ratio stayed around 0.1 to 0.2, which is well below the critical threshold of one, and 88 percent of post-onset forced selling landed inside thirty minutes.
The detail worth remembering is where the pressure went. 63 percent of that forced selling was absorbed off-book by the venue's backstop rather than by the visible order book, which pushes the measured branching ratio down precisely at the climax.
For a trader this means the book you can see is not the liquidity that is actually absorbing the event. For an engineer it means cascade metrics computed from visible liquidity will systematically overstate the danger at the moment it matters.
What to check before trusting any stop-loss setup
Four things, in order of how much they usually matter.
Confirm which price feed your stop reacts to, and which feed governs liquidation. If they differ, compute the historical disagreement rather than assuming it is small.
A practical way to do it: pull one minute candles for the last month and take the maximum positive gap between mark and last price inside each hour. In quiet hours the gap is a few basis points. Around liquidation clusters it can pass your entire stop distance, and that is the hour the stop gets skipped.
Decide whether your exit needs certainty or price. A market order buys certainty and pays spread plus slippage. A limit order buys price and risks not exiting.
Size so the maintenance boundary is far from your stop, not adjacent to it. If liquidation sits 30 basis points behind your stop, the entire question becomes which feed updates first.
Watch funding as a slow trigger. It moves the margin boundary between settlements, so a position that was comfortable at entry can drift into breach without a single dramatic candle.
Four checks, four numbers, and none of them requires predicting direction. That is the useful part: liquidation risk is a property of your configuration and the venue's plumbing, not of your view on the market.
Conclusion
A stop-loss is a conditional instruction evaluated on one price series and executed on another. Liquidation is a margin test evaluated on the mark. The distance between them is where slippage, latency, liquidity and funding all get a vote.
None of this argues against using stop-losses. It argues against treating them as a liquidation boundary. The boundary is set by maintenance margin, and everything else is an attempt to reach the exit before the engine reaches you.
References
BTCC Academy, "Why Stop-Losses Don't Always Prevent Liquidation and How to Avoid It," in Crypto Basics: https://www.btcc.com/en-CA/academy/crypto-basics/why-stop-losses-dont-always-prevent-liquidation
Forecasting 8(5), 76, "Delayed Marks, Funding Memory, and Forecasting Liquidation-Tail Risk in Crypto Perpetual Futures," 2026: https://www.mdpi.com/2571-9394/8/5/76
arXiv:2608.03616, "Measuring the engine of a liquidation cascade: subcritical branching inside a first-order transition," 2026: https://arxiv.org/abs/2608.03616
