Binance's $6.34B fix: paid, not proven
Binance says it has covered the $6.34B hack from company funds. The proof users can check themselves is still 40-50 hours away.
Binance said Thursday it has finished covering the $6.34 billion Oct. 29 hack entirely from company funds. The exchange published a new proof-of-reserves snapshot the same day, covering 198 tokens, up from just 10 in its first snapshot two weeks earlier.
What Binance actually paid with
The wording is specific: Binance "completed coverage" of affected assets, not recovery of stolen funds. It drew on three pools to replace the tokens: SAFU, a portion of its futures insurance fund above required risk levels, and its own corporate treasury.
The exchange has committed to refilling SAFU back to roughly $1 billion after the partial draw.
- Binance pledged more than $6.34 billion in company funds to cover the hack, per its Thursday statement.
- The Nov. 12 proof-of-reserves snapshot spans 198 tokens, versus 10 tokens in the Oct. 31 snapshot.
- Binance reported 90% coverage shortly after the breach, then 95%, then 98%, before Thursday's claim of completion.
- The full zero-knowledge proof needed to verify 1:1 backing takes an estimated 40 to 50 hours to generate.
- Withdrawals first reopened Nov. 1 with bitcoin and have continued in phases since.
The gap between a claim and a proof
The obvious read is that Binance made customers whole and the crisis is over. The timeline supports that framing on its face: three weeks from breach to a stated 100% coverage is fast for the largest theft in crypto history.
But completion and verification are two different events, and Binance has only delivered the first one. The exchange says the snapshot shows assets "fully accounted for." Users cannot check that themselves until the zero-knowledge proof lands, two days out from the announcement.
That sequencing matters. Binance chose to announce completion before the tool that lets anyone outside the company confirm it was ready. The gap between the words and the proof is where the hack's real cost still sits.
A statement of solvency and a mechanism for proving solvency are not interchangeable, and Binance is currently asking customers to accept the first while the second is still being built.
What the announcement leaves out
Thursday's update says nothing about how much of the stolen $6.34 billion has actually been recovered from whoever carried out the Oct. 29 theft. No attacker is named. No recovery figure is given.
Covering customer balances from treasury and insurance funds solves the user-facing problem. It does not touch the separate question of whether Binance, or law enforcement, ever claws back the stolen assets.
Withdrawals also remain on a phased schedule rather than fully open. Binance says it will share details "once confirmed," language that has described the rollout since Nov. 1 without a fixed end date attached.
Signals that would confirm or break this
The next concrete test is the zero-knowledge proof itself, due roughly two days after Thursday's statement. If it validates the 198-token snapshot at 1:1 backing, the coverage claim moves from assertion to verified fact.
If the proof slips past the 40-to-50-hour window Binance gave, or comes back showing a shortfall, the "fully covered" framing stops holding.
- Whether the zero-knowledge proof publishes within 40-50 hours and confirms 1:1 backing across all 198 tokens.
- Whether Binance discloses any recovery amount from the attacker, separate from the treasury-funded coverage.
- Whether withdrawal phases close out with a stated end date, rather than continuing indefinitely as "in progress."