
Binance Deploys $6.34B to Cover Incident Losses, Publishes New Proof of Reserves
Binance says it has fully covered assets affected in a security incident, using $6.34 billion from SAFU, its futures insurance fund and treasury. A new Proof of Reserves snapshot is live.
In brief
- Binance committed more than $6.34 billion of company funds to cover losses from the incident.
- The new Proof of Reserves snapshot, taken at Thu 12 Nov, 07:00 (GMT+7, 24h), covers 198 tokens.
- Withdrawals are reopening in phases; Binance says further updates will follow once confirmed.
What happened
Binance said it has finished covering the user assets affected in a security incident.
The exchange committed more than $6.34 billion of company funds to the effort, according to its announcement.
The money came from three places: a partial draw on the Secure Asset Fund for Users (SAFU), an emergency reserve for customers; part of Binance's futures insurance fund above the level its risk rules require; and the company's own treasury.
Binance said it sourced the affected tokens through market and over-the-counter (OTC) channels.
It also pledged to top SAFU back up to about $1 billion.
A new Proof of Reserves (PoR) snapshot was taken at Thu 12 Nov, 07:00 (GMT+7, 24h) and covers 198 tokens.
A zero-knowledge proof for it should take about 40 to 50 hours to generate because of the computing load.
Once that proof is ready, holders of the affected tokens will be able to check for themselves that their assets are backed at least 1:1.
Withdrawals are reopening in stages, and Binance said it will give more updates when dates are confirmed.
A very small number of tokens Binance no longer supports were also hit.
Those will go through the normal delisting process, and holders will be covered.
Why it matters
The size of the commitment makes this one of the largest user-asset backstops an exchange has announced.
Drawing on SAFU, the insurance fund and treasury spreads the cost across reserves meant for exactly this kind of event.
The phased withdrawal restart is the part holders feel first.
Until all withdrawals are open, users of the affected tokens cannot move them freely, even if the backing is in place.
The PoR snapshot gives a public record at a fixed time.
The zero-knowledge proof is the check that ties that record to real balances without revealing individual user data.
The incident lands in a busy week for exchange risk.
South Korea's FSC has moved to let exchanges freeze withdrawals on suspected hacks, and US lawmakers are seeking records from major venues including Binance, as reported in the Senate panel's request.
What to watch
The zero-knowledge proof should appear in roughly two days.
Holders of affected tokens can then verify their 1:1 backing on the PoR site.
Binance has not given a full timetable for withdrawals.
Watch for its next update on which assets and regions reopen.
SAFU's return to about $1 billion is a separate milestone.
Until then, the emergency reserve is running below its target size.
For users of Binance's tokenized stocks, a separate schedule applies.
The exchange will support an 8-for-1 split of Sandisk (SNDK) for SNDKB holders, with a snapshot at Fri 20 Nov, 08:00 (GMT+7, 24h), as set out in the bStocks split notice.