Curriculum·S209 The Centralized Exchange in Depth·about 31 min
Operating on a CEX professionally
By the end of this lesson you can
- →Configure an account once, in the order that makes each setting effective
- →Run the operating routine that keeps the configuration true over time
- →Produce the dependency diagram this course requires, and read it for the single point
- →State the standing rules that need no judgment at the moment they apply
Sophomore · enrolled learners
This lesson opens with Everything in this course, on one day.
- What happened
- This lesson's opener is the course assembled rather than a new event, and it is labeled as such. On 10 October 2025, more than $19B of leveraged positions were liquidated within 24 hours across more than 1.6 million accounts, by CoinGlass's count. Order-book data on Binance showed depth on the pairs measured falling by around 98 percent. Collateral assets on Binance repriced on its own spot market, with USDe printing near $0.65 and wrapped staking tokens far lower, cutting equity and forcing liquidations in positions they were only backing. Hyperliquid used auto-deleveraging to close $2.1B of positions in 12 minutes, ranking on profit, leverage and size. Binance acknowledged platform-related issues, traders documented reduce-only orders rejected for well over an hour, and Binance announced compensation the next day for a 40-minute window.
- The decision point
- Every mechanism in this course operated at once: the depth collapse, the order type behavior, the cross-collateral coupling, the waterfall ending in auto-deleveraging, and the discretionary remedy afterwards. Each did what its documentation describes, and the venue itself also strained, so orders sent during the event could not be counted on to arrive. On this lesson's reading, what an account holder could still rely on that night was what had been configured beforehand.
- Recorded loss
- $19,000,000,000
What you will be able to answer
- →In what order do you configure an account?
- →What is the single point in a dependency diagram?
- →Name the standing rules.
- →Why did prepared accounts come through 10 October 2025?
Orientation and Year One are open: anyone can read them without an account. From Year Two onward the lessons are for enrolled learners, because progress through the later years only means anything if it is tracked against a record.
It is free. We do not sell the list and there is nothing to buy at the end of it.
Sources and review
- https://www.coingecko.com/learn/october-10-crypto-crash-explained
- https://www.coindesk.com/research/market-spotlight-the-19-billion-liquidation-that-shook-crypto
- https://cointelegraph.com/research/exclusively-obtained-orderbook-data-reveals-details-about-usde-crash
- https://www.binance.com/en/support/announcement/detail/0989d6c7f32545bfb019e3249eaabc3f
- https://www.coindesk.com/markets/2025/10/12/binance-to-compensate-users-affected-by-crash-in-wbeth-bnsol-and-ethena-s-usde
- https://www.forbes.com/sites/boazsobrado/2025/10/21/locked-out-and-liquidated-traders-blame-binance-for-19-billion-crash/
- https://arxiv.org/abs/2512.01112
- https://www.coindesk.com/markets/2025/10/11/how-adl-on-crypto-perp-trading-platforms-can-shock-and-anger-even-advanced-traders
Confidence medium·Volatility high·Reviewed 2026-10-22·Owner unassigned
Contested
An earlier version said every mechanism worked as documented, nothing required a failure and no venue broke its own rules. The record does not support the last two: Binance acknowledged platform-related issues and Forbes reported traders' logs of rejected reduce-only orders. That prepared accounts came through is this course's reading, not a measured finding; no source compares outcomes by configuration.
The configuration steps here reflect settings commonly available across major venues at the review date. Names, availability and defaults differ and change. Teach the property each setting buys, and re-check availability at review.
This lesson assembles the course rather than introducing new material, and its autopsy is labeled as such. Do not let a revision present it as a distinct incident.