Binance Covers $6.3B Hack Loss, but Its Bitcoin Cushion Is Thin
- Published
- Updated
Binance said it has finished covering the customer assets drained in its October 29 hack, and it published a new proof-of-reserves snapshot on Nov. 12. The snapshot has not yet been independently checked by users because Binance has not published the zero-knowledge proof needed to verify it.
Key claims & sources
What it means
Binance’s proof-of-reserves system is the mechanism users and the market watch to see whether customer balances are matched by assets on hand, and that matters most after a security incident. The Oct. 29 hack put that mechanism under scrutiny because the exchange had to show it had restored customer balances. The Nov. 12 update places the focus on whether the reserve snapshot can be independently checked, not just announced.
For Binance customers, the practical effect is that the exchange says the affected balances have been filled back in, while outside verification is still pending. That means users can see a public reserve update, but they cannot yet reproduce the check on their own. The next step is the release of the zero-knowledge proof that would allow verification of the snapshot. (per unchainedcrypto.com)
This episode sits at the center of the trade-off between exchange self-reporting and transparent verification, which has been a recurring issue for large centralized venues. A published reserve snapshot can reassure users, but without an independently checkable proof it still depends on trust in the exchange’s disclosure. That tension is especially sharp after a hack, when the question is not only whether assets were replaced but whether the replacement can be demonstrated in a way outsiders can verify.
Market reaction i
Bitcoin rose 0.1% in the 4 hours after the first headline, after a flat 2 hours before.
43 prices, one every 30 minutes
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 |
|---|---|---|
| 16 days ago | Binance CEX · Key Leaked via Infrastructure incident | $6.4B |
| 16 days ago | Binance · DevOps Engineer’s laptop compromised incident | $6.3B |
| 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 |
4307 incidents stored · 2 were as large as this one or larger ($6.3B)