- No 100%
- Yes <1%
Binance expects to partially deploy SAFU fund within 24 hours after $6.3 billion breach
- Published
- Updated
- Since then
- 5 new reports
- In
- Bitcoin
Binance used part of its SAFU reserve after the $6.3 billion hack, moving 7,499 BTC out of the fund and leaving about 7,500 BTC behind in the wallet. Fresh coverage adds that the transferred coins later moved again to an unlabeled address, and one report places the remaining SAFU balance at half of the fund’s post-conversion size in February.
Key claims & sources
What it means
Binance moved 7,499 BTC out of the wallet on Oct. 31, halving the fund to about 7,500 BTC, and says 95% of lost assets are already replenished through a mix of token backing and OTC sourcing. Depositors regain access to balances faster than in past exchange collapses, but the exchange has given no date for rebuilding the reserve to its prior $1 billion target. Anyone relying on SAFU as a backstop now holds a claim against a fund that is thinner and untracked.
An emergency fund that exists to reassure users only works if its holdings and movements are legible, and watching 7,500 BTC leave a known SAFU address for an unlabeled wallet cuts against that purpose. Binance controls the keys, the disclosure timing and the accounting, which is the same single-custodian concentration crypto was meant to route around. The exchange's quick partial payout shows operational strength, but opacity about where the remaining reserve sits leaves the question of real backing versus stated backing unresolved.
The next marker is whether Binance publishes a full accounting of the SAFU drawdown and a concrete restoration date for the $1 billion target, something it has not yet committed to. Equally telling is whether the 7,500 BTC sent to the unlabeled address on Nov. 3 resurfaces in a disclosed Binance wallet or stays untracked by on-chain analysts. Either outcome will show whether SAFU still functions as a transparent insurance pool or has become a reserve managed on trust alone.
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.5 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 |
4280 incidents stored · 0 were as large as this one or larger ($6.3B)