# The Great Crashes, Part 3 — 10/10, The $19B Day

> A forensic post-mortem of October 10, 2025: how a tariff shock, a Binance index quirk, and looped USDe collateral produced crypto's largest liquidation.

- Source: https://www.steadyrain.xyz/en/articles/great-crashes-3-october-2025-liquidation/
- Publisher: Steady Rain
- Author: 0xYatha
- Published: 2026-07-13T05:53:55.797Z
- Categories: History, DeFi
- Language: en

## Introduction

At 21:15 UTC on October 10, 2025, roughly $3.21 billion in leveraged crypto positions were closed inside a single sixty-second window. By the end of the day, Coinglass tallied more than $19 billion in forced closures across some 1.6 million accounts — the largest single-day liquidation event ever recorded in this market. Perpetual futures open interest fell from around $217 billion to $123 billion, a 43% contraction. Hyperliquid alone shed 57% of its open interest, from $14 billion to $6 billion. The average token in CoinDesk Data's tracked universe fell around 47% intraday, exceeding the peak-to-trough averages of May 2021.

Numbers of this size invite a simple story: leverage got too high, a shock arrived, the market cleared. That story is not wrong, but it is the least interesting version of what happened. The event was legible only through the interaction of three distinct failure modes stacked on the same weekend: a macro trigger in the form of a US tariff announcement, a venue-specific price artifact on Binance's internal index that printed USDe at $0.65 and — per widely repeated but not-yet-primary-sourced reporting — wBETH at nearly \~-88% only on that venue, and a well-fed leverage loop built on synthetic-dollar collateral treated as if it were cash.

This is Part 3 of our Great Crashes series. Where Part 1 walked through the 2020–2022 arc of on-chain leverage failures and Part 2 dissected the FTX collapse as an intermediary-solvency event, October 10, 2025 belongs to a third category: an infrastructure event, in which the plumbing of margin engines and collateral policies became the story. What follows is a mechanism-first post-mortem, with the numbers anchored to the sources that support them and the disputed claims flagged as disputed.

## The trigger: a tariff post into a record-leverage market

Coming into that Friday, total crypto perpetual open interest sat near a record $217 billion. Bitcoin had peaked earlier in the session at $122,574. The set-up was structurally fragile in a boring, familiar way: a lot of directional positioning financed by a lot of margin, spread across a lot of venues, on a weekend when traditional-market hedging is unavailable and market-maker balance sheets are lightly staffed.

The trigger was exogenous. On the evening of October 10, US President Trump posted on Truth Social announcing 100% tariffs on Chinese imports, taking the total tariff burden on Chinese goods to 130% and effective November 1, 2025. Global risk assets sold off. Crypto, as it now typically does under a macro shock, moved first and most.

According to Amberdata's reconstruction cited by CoinGecko, the first liquidations were a slow trickle. The violent phase began at 20:50 UTC: $6.93 billion in positions were liquidated over the next forty minutes, a rate of roughly $10.39 billion per hour. The peak was that 21:15 UTC minute — $3.21 billion in a single sixty seconds. By the time it was over, BTC had touched $104,782 on CoinGecko's series (CoinDesk's CADLI reference rate registered a slightly higher low of $106,560, a discrepancy worth flagging because it tells you the market itself did not agree on a single clearing price). ETH bottomed near $3,436 to $3,551 depending on source. SOL briefly lost more than 40% of its value intraday before stabilizing near $174. Total crypto market cap shed roughly $350 billion.

The macro trigger explains why the market went down. It does not explain why it went down that fast, or why some assets printed prices that had no obvious reference in spot markets. For those questions we need to look at the venues.

## The cascade: cross-margin, thin books, and the arithmetic of forced selling

*[Figure: img1]*

Once BTC and ETH began falling, the mechanics of cross-margined perpetual futures took over. On most large venues, a trader with a portfolio of positions posts a single pool of collateral. Maintenance margin is calculated against the mark-to-market value of every position at once. A move in one leg does not need to blow through its own margin threshold to force liquidation — it can trigger liquidation across the portfolio by dragging the aggregate equity below the aggregate maintenance requirement.

That mechanism is efficient in normal conditions. It is a cascade amplifier under stress. As BTC fell from the $122K area toward $110K, portfolios that were net-long across many tokens simultaneously lost margin buffer against every position. Liquidation engines began forced-selling, and forced-selling into a thinning book is the classic recipe for gap risk.

Order-book depth is the second ingredient. Per Coinwatch data cited by CoinDesk, visible top-of-book depth on large-cap assets — those with fully diluted valuation above $5 billion — "evaporated" during the intraday window. On a normal day, market makers post two-sided quotes because the spread more than compensates for adverse-selection risk. In a fast market on a weekend with correlated selling across every asset, that math flips: quoting is a way to be run over. Rational market makers widen spreads or pull quotes entirely, precisely when liquidity is most needed.

The result is the familiar shape of a cascade. Forced selling drops price faster than orderly discovery would; the price drop marks other positions to values that trip their own maintenance thresholds; those liquidations sell into a book that is now even thinner. The 21:15 UTC minute — $3.21B in sixty seconds — is what this cascade looks like at peak intensity.

None of this is unique to October 10. It has been the mechanical anatomy of every major crypto crash since perpetuals became dominant. What made this event distinct began on one specific venue.

## The Binance fault line, part I: the index price

*[Figure: img2]*

Perpetual futures do not liquidate positions against the raw last-traded price on the venue's own order book. If they did, a determined attacker could push the local price around and force liquidations at will. Instead, most venues compute a **mark price** from an **index** that is some function of prices observed on external reference markets. Positions are liquidated when equity falls below maintenance margin measured against this mark price. The index is, in effect, the venue's model of "the real price."

The design decision that matters most is which sources feed the index and how they are weighted. Cap-and-median approaches — take the median of five or six external prices, cap the weight of any single source — are robust to a single feed going bad. Weighted-average approaches without hard caps are efficient in normal markets but expose the engine to whichever source most quickly reflects a stress event.

According to CoinDesk Research, USDe depegged to $0.65 on Binance during the cascade and this depeg "acted as a secondary liquidation trigger." Widely repeated commentary — including the CoinGecko treatment of the January 2026 dispute between OKX's Star Xu and Binance — has described the print as venue-specific: USDe's price on other venues at the same moment was materially closer to par. The article-topic brief also references a wBETH print at approximately \~-88% on Binance only. We have not been able to verify the wBETH figure or the specific mechanics of the index methodology from primary sources within Binance's own announcement; the announcement page is on our reference list but could not be retrieved in a form we could quote. We flag both details as pending primary-source verification, and we treat the following as an interpretation rather than an established fact: if the USDe and wBETH prints were venue-specific, the most parsimonious explanation is an index/oracle design in which internal Binance market prices were sufficiently weighted to allow a local dislocation to propagate into the mark price used for margining.

Whichever the precise mechanism, the consequence is straightforward. Any trader whose portfolio included USDe as collateral saw the mark value of that collateral collapse to $0.65 for margin purposes, regardless of whether they could redeem or sell it elsewhere near par. Any trader with wBETH positions marked to an -88% print faced instantaneous liquidation on a scale that would not have been triggered by any plausible spot-market print of the same asset. The secondary cascade fed on the primary one.

Reporting subsequently indicated that Binance introduced index-weight changes and paid compensation to affected users. A figure of roughly $283 million in compensation has circulated in secondary discussion of the event and appears in our topic brief; we could not confirm it against Binance's own announcement text within the sources available to us, and we flag it as an open question rather than a settled number. The direction of travel — capping single-venue weights, tightening circuit breakers, restricting internal-index dependencies for stress prints — is the standard response to this class of failure. Whether the specific fixes are structural or cosmetic is not knowable without the primary announcement.

## The Binance fault line, part II: the leverage loop

*[Figure: img3]*

The second Binance-adjacent question is whether the platform's collateral policy and yield promotions contributed to the size of the cascade, independent of the index issue. This is the substance of OKX CEO Star Xu's public accusation on January 31, 2026, which — per CoinGecko's reporting — targeted Binance's 12% APY promotional campaign on USDe and its treatment of USDe as collateral equivalent to USDT and USDC.

To evaluate this claim we have to separate USDe as an asset from how a venue chose to use it.

### USDe is not USDT

USDe is a synthetic dollar. It maintains its peg not through cash and Treasury bills held in a bank account, but through a delta-neutral hedge: long spot exposure to underlying assets combined with short perpetual futures positions on those same assets, with the funding-rate spread producing yield. Under normal conditions the peg holds because the hedge holds. Under stressed conditions — when funding turns violently, when perp liquidity disappears, or when the venue running the short leg itself experiences a mark-price anomaly — the hedge can decouple from the peg. That is not a defect specific to USDe; it is the definitional property of any synthetic dollar that is not literally cash.

A margin engine that treats USDe as identical to USDT is implicitly asserting that its peg is as robust as a cash-collateralized stablecoin under all conditions the engine cares about. In tail scenarios that assertion is false.

### The loop

The mechanism described in Xu's public statements, summarized by CoinGecko, is a straightforward carry trade compounded through re-hypothecation:

1. Convert USDT (or USDC) into USDe, earning the promoted \~12% APY.
2. Post USDe as collateral, borrow USDT against it.
3. Convert the borrowed USDT into USDe and earn yield on that too.
4. Repeat.

At each turn of the loop, the trader's notional USDe holdings grow while their initial capital stays fixed. On a static basis this produces the arithmetic that Xu described — apparent yields in the 24% to 70%+ range, depending on how many turns are stacked and what borrow rates apply. We treat the 70%+ upper bound with caution, since it comes from a competitor CEO's public argument and has not been independently verified in our source set.

The important point is not the exact peak yield but the structural exposure. Every turn of the loop increases the trader's exposure to two joint events: USDe deviating from par, and the borrow leg being called. When USDe printed $0.65 in the venue's mark price, both events occurred simultaneously for every looped trader. The collateral value collapsed and the borrow position became under-margined at the same instant. Cross-margin then propagated that shortfall across every other position in the portfolio, and the forced-selling of those positions contributed to the broader cascade.

### The order of events

Binance's stated defense, again per CoinGecko, is that the macro shock came first and that high aggregate leverage and evaporated liquidity — conditions that were market-wide and not attributable to any single venue's product design — did the rest. The available excerpt of Binance's rebuttal cuts off before the full argument is on the record, and we do not have the primary document.

There is genuine substance to the defense. Xu's own timeline, as reported, has BTC declining approximately 30 minutes before USDe depegged, which means the leverage loop cannot have initiated the cascade — the tariff shock did. And the record $217B in aggregate open interest was not built on Binance alone; every large venue contributed. Any sufficiently severe macro shock into that positioning would have produced a very large liquidation event regardless of USDe's role.

The narrower and more defensible version of the criticism, in our reading, is not that Binance caused the crash but that specific product design choices — a promotional yield campaign that concentrated collateral into USDe, an index methodology that permitted a single-venue print to drive mark prices, and a margin policy that treated a synthetic dollar as equivalent to cash-collateralized stablecoins — amplified the cascade beyond what the macro trigger alone would have produced. That version is compatible with both the timeline evidence and the venue-specific price artifacts.

## Hyperliquid and the price of using ADL

*[Figure: img4]*

The event's second infrastructure story unfolded on Hyperliquid, which experienced its first **auto-deleveraging** (ADL) event in roughly two years. Understanding what ADL is, and what it does to counterparties, is central to reading this part of the event.

### What ADL is for

When a liquidation cannot be absorbed by the order book at prices better than the bankruptcy price of the liquidated position, the venue's insurance fund is drawn on to cover the shortfall. If losses exceed the insurance fund's capacity, the venue faces a choice between three unpleasant options: default on the profitable counterparty (destroying the exchange's credibility), socialize the loss across all profitable traders (spreading the damage widely and predictably), or auto-deleverage — force-close a selection of the most profitable counterparty positions at the bankruptcy price of the underwater position.

Hyperliquid, like most perpetual venues, uses ADL as a backstop. It is disclosed. Sophisticated participants know it exists. The controversy is not about its legitimacy but about its incentive properties.

### What ADL does to market makers

Market makers on perp venues typically run books that are close to delta-neutral. A common structure is: hedge inventory built up from providing liquidity by taking offsetting positions on the same or another venue, so that the market maker earns spread and rebates without carrying directional risk. This is the entire business model. It requires the hedge to remain in place.

ADL breaks that requirement in the worst possible moment. When a market maker's position is selected for auto-deleveraging — typically because it is among the most profitable positions on the opposite side of the failed trade — the position is force-closed at the bankruptcy price. The market maker's hedge is now missing one leg. The other leg, sitting on a different venue or in spot inventory, is suddenly a naked directional position in a market that has just experienced its largest cascade on record.

Reporting on the specific composition of Hyperliquid's ADL selections during the event and which market-maker books were affected is not detailed in the sources available to us, and we do not name specific firms. The mechanism, however, is well understood. The 57% contraction in Hyperliquid's open interest — from $14B to $6B — is consistent with a story in which some fraction was forced closure via ADL and the rest was voluntary book-flattening by participants who saw what had just happened and rationally reduced size.

### The design tradeoff

The alternatives to ADL are not obviously better. Socialized loss — pro-rata haircuts on profitable trader balances — spreads the damage widely and destroys the trust of exactly the sophisticated participants a venue needs to keep. Larger insurance funds cost money to capitalize and are, in the tail, always insufficient against a truly unbounded loss. Pre-funded default waterfalls similar to those used by regulated derivatives clearinghouses require capital contributions that most crypto venues have not asked their members to make.

The honest reading is that ADL is a rational choice for a venue that wants to remain solvent through a tail event, and a serious hidden risk for market makers who provide the two-sided liquidity that keeps the venue functional in normal times. Every large ADL event increases the market-maker haircut on future participation. It shows up as wider spreads and thinner books in the next stress event. This is a form of quiet cost that does not appear on any post-mortem but that everyone in the business notices.

## Structural lessons

*[Figure: img5]*

Three lessons sit above the individual venue stories.

### Oracle and index design is margin engine design

An index is not neutral infrastructure. It is a specific claim about which prices are "true" for the purpose of taking collateral away from customers. When that claim is wrong — when a venue's own market can dominate its own index during a stress event — the margin engine becomes a mechanism for manufacturing losses that the underlying assets did not require.

The design principles that mitigate this are not new: source diversity, hard weight caps on any single venue, median-based aggregation, circuit breakers that halt liquidations when the index diverges from a robust reference, and post-hoc reconciliation for prints that clearly deviate from external evidence. The question October 10 raises is not whether these principles are known — they are — but whether they are consistently applied under the pressure of product velocity and competitive yield offerings. The answer, evidently, is not yet.

### Synthetic-dollar collateral is a policy choice, not a technical one

Treating USDe as collateral-equivalent to USDT is a business decision made by a venue's risk committee, not a property of USDe itself. USDe as an asset has its own well-documented risks, but it is not obliged to be posted as margin at 1:1 weighting against cash-collateralized stablecoins. A venue that wants to support USDe as collateral has options: haircut it (accept USDe worth $1 as $0.90 of margin), cap the maximum share of a portfolio's margin that can be sourced from synthetic dollars, or restrict its use to cross-margin isolated in specific product categories.

The 12% APY promotion combined with equivalent-collateral treatment created a large concentrated pool of looped USDe collateral. That concentration was itself the risk, more so than USDe's design. A synthetic dollar is a fine instrument. It becomes a systemic exposure when a venue's incentives, promotions, and collateral policy conspire to concentrate positioning in it during quiet times, without commensurate margin haircuts to compensate for stress-scenario correlation.

### ADL is a tax on hedged liquidity

For the reasons discussed, ADL converts hedged books into naked ones exactly when hedging matters most. There is no obvious better mechanism given the constraints of an unregulated derivatives venue, but the cost is real and cumulative. Each large ADL event trains market makers to run smaller books, quote wider, and pull faster in stress. That is the same as saying each large ADL event thins the book in the next crisis. The lesson is not that Hyperliquid did anything wrong; it is that the ADL toolkit, deployed at scale, produces a market structure that is more brittle than the one a fully capitalized default waterfall would produce. Whether the industry will move toward that model is an open question about capital costs and regulatory posture, not about technical feasibility.

## What still needs to be established

We have written this piece with more epistemic caveats than usual because the source base is incomplete. The specific mechanics of Binance's index methodology on the day, the exact terms and size of any compensation program, the details of the wBETH print, and the composition of Hyperliquid's ADL selections are all questions where the primary documents either exist and were not accessible to us, or have not yet been produced. A more complete accounting will require Binance's official announcement text, Hyperliquid's own post-mortem if one is produced, and — ideally — independent forensic reconstruction of the index feeds during the critical minutes.

Two open questions matter most for anyone building or trading on these venues. First: given that a single venue's internal market can, under stress, dominate its own margin index, what design changes are needed to make single-venue price artifacts non-fatal to cross-venue traders? Second: given that synthetic-dollar collateral behaves categorically differently from cash-backed collateral in tail events, is the industry converging on a margin-haircut standard, or will each venue continue to make idiosyncratic choices whose costs are only revealed after the next cascade?

October 10, 2025 was, by every quantitative measure available, the largest liquidation event this market has ever experienced. It was also — by a margin that will grow as more of the primary record becomes accessible — the clearest recent case of infrastructure design amplifying rather than dampening a macro shock. Whether the industry treats it as such is the real subject of Part 4.