Binance Commits $6.34 Billion to Cover October Breach Losses

Binance says it has fully covered customer losses from its Oct. 29 security breach, committing more than $6.34 billion against losses the exchange values at roughly $6.3 billion. The commitment, announced Nov. 12, draws on three internal sources rather than recovered funds; the announcement did not state how much, if anything, has been retrieved from the attackers.

The exchange listed its Secure Asset Fund for Users (SAFU), excess capital from its Futures insurance fund, and corporate treasury assets as the sources of coverage. Binance also plans to rebuild SAFU to approximately $1 billion. The absence of any recovery figure is notable; $6.34 billion represents a commitment to absorb losses, not a clawback from the perpetrators.

The FBI has attributed the theft to North Korea and tracks the activity under the label "TraderTraitor." Binance estimated its hot wallets were compromised at about 4:05 p.m. ET on Oct. 29 (20:05 UTC). Attribution to a state-linked actor typically narrows the practical avenues for recovery, which places the full burden of the $6.3 billion loss on Binance's own balance sheet.

What does the new Proof of Reserves show?

Binance published an updated Proof of Reserves snapshot covering 198 tokens, timestamped 00:00 UTC on Nov. 12 (7 p.m. ET on Nov. 11). The snapshot alone, however, is not the verification mechanism. The full zero-knowledge proof was still being generated at the time of the announcement, with completion expected in roughly 40 to 50 hours.

Once available, holders of affected tokens can use the proof to verify at least 1:1 backing of their balances. That verification window matters: until the zero-knowledge proof is live, customers cannot independently confirm the reserves claim and must rely on Binance's representation. A 198-token snapshot covers breadth, but a snapshot without the cryptographic proof is a promise with an audit pending.

How sustainable is the coverage?

The $6.34 billion commitment exceeds the estimated $6.3 billion in losses, a margin of about $40 million, or well under one percent of the total. The structure of the coverage also raises questions about future resilience. SAFU is being drawn down and then replenished to about $1 billion — roughly one-sixth of the loss it just helped absorb.

The Futures insurance fund contribution has its own consequences. Diverting excess insurance capital to cover a hot-wallet breach reduces the buffer protecting futures traders against liquidation events, shifting risk from one customer segment to another. Binance did not quantify how much each source contributed, which limits outside assessment of the exchange's remaining cushion.

For a frame of reference, the committed sum of $6.34 billion is more than six times the size SAFU will hold after replenishment. Any repeat incident of comparable scale would therefore test whether the current funding structure, rather than recovered assets, can absorb a second shock.

The operational takeaway is plain: customers are covered on paper today, but independent verification arrives only when the zero-knowledge proof completes, expected within about two days of the Nov. 12 announcement.