A Decade Ago, a $6.3 Billion Hack Would Have Sunk Binance & BTC, Bitwise CIO Says
- Published
- Updated
- Since then
- 12 new reports
- In
- Exchanges
Binance’s October 29 hot-wallet hack triggered withdrawals, reserve checks, and public statements from other exchanges and analysts. New reporting adds that the exchange later posted positive net inflows, that most impacted tokens were replenished, and that insurance may cover only a limited share of the losses.
Key claims & sources
What it means
Proof-of-reserves checks became an industry norm after FTX collapsed in November 2022 without warning, leaving customers unable to verify that deposits were backed. Binance, the largest exchange by volume, had already run periodic attestations before the October 29 hack, but this is the first time it has paired a zero-knowledge proof with a crisis of this scale, letting any of its users cryptographically check 1:1 backing for ten major tokens without exposing other customers' balances.
For Binance's roughly 335 million account holders, the practical change is that they can now self-verify holdings in BTC, ETH, BNB, SOL and XRP rather than take the exchange's word for it. Binance says 98% of impacted tokens have been replenished, and net flows swung from $5.28 billion in outflows to $2.3 billion in inflows as withdrawals resumed. Separate reporting suggests insurance may cover only a limited share of the $6.3 billion loss, meaning the exchange's own reserves carry most of the repair.
Binance itself was careful to call the snapshot a reserves check, not a solvency audit, and that distinction matters more than it sounds. A proof of reserves confirms assets exist at a point in time; it says nothing about liabilities, off-balance-sheet obligations, or whether the same funds could be double-counted across products. Treating cryptographic snapshots as a substitute for independent, liability-inclusive audits lets exchanges claim transparency while regulators and depositors still lack the fuller picture that traditional audited financial statements would provide. (per cryptopolitan.com)
Outside analysts reviewing the blockchain trail say they can see repeated drains from Binance's hot wallets but cannot determine from public records alone what internal signing controls or transaction limits were in place when the theft occurred. Whether Binance discloses or submits to independent review of those wallet-signing policies, rather than relying on after-the-fact reserve snapshots, will determine if this episode changes custody practices industry-wide or simply becomes another costly breach absorbed and moved past. (per cointelegraph.com)
Market reaction i
Coverage timeline
Every piece in order, with the time its news medium declares — if it is not believable we use ours and say so — and what it added to what was already known at that point. Arriving first is not the same as adding something.
Thefts of a similar size
| When | What happened | Figure |
|---|---|---|
| 5.9 years ago | LuBian · Weak key generation incident | $3.5B |
| 5.6 years ago | Thodex · Scam incident | $2.5B |
| 5.4 years ago | Africrypt · Scam incident | $2.3B |
| 6.4 years ago | Wirecard · Scam incident | $2.1B |
| 5.2 years ago | BitConnect · Scam incident | $2B |
4285 incidents stored · 0 were as large as this one or larger ($6.3B)