SAFU — "Secure Asset Fund for Users" — is Binance's self-insurance fund, established in July 2018 with an allocation of 10% of trading fees, capitalized at over $1 billion by 2026. It is a fund the exchange holds in cold storage to cover unexpected user losses from security incidents or platform failures. The name became a meme ("funds are safu") before becoming an actual fund.
What SAFU has actually been used for
Three notable invocations:
May 2019: Attackers exfiltrated 7,000 BTC from a Binance hot wallet (about $40M at the time). CZ announced within hours that SAFU would cover the loss; no user account was debited. This was the first major test and it worked.
October 2022: BSC bridge hack — an attacker exploited the cross-chain bridge to mint 2 million BNB. The exploit was contained quickly, but SAFU was placed on standby in case user losses had occurred.
September 2023: Various smaller incidents involving phishing attacks where users lost funds on Binance-listed assets (not Binance's own custody). Binance has occasionally extended SAFU coverage to these out-of-scope incidents at its discretion.
What SAFU is not
SAFU is not FDIC insurance. There is no statutory obligation to cover losses; the fund is deployed at Binance's discretion, on its own timeline, for whatever portion of the loss it chooses. The May 2019 incident set a precedent of "full coverage, fast" but no contract requires that for future incidents.
SAFU also does not cover user error. Lose your private key, get phished into signing a malicious transaction, send funds to the wrong address — none of these are SAFU events. The fund covers platform-side incidents, not user-side mistakes.
The competitor positions
Coinbase maintains a similar internal reserve, though without the explicit "1B+" framing or the discrete fund name. Crypto.com established a "User Asset Reserve" in 2022 with similar structure. Kraken has not established an analogous fund, instead emphasizing institutional security practices.
For a US-resident holder comparing exchanges, SAFU is a positive signal but not a complete one. The combination "regulated exchange + PoR + self-insurance fund" is what to look for. Binance.US, Coinbase, and Kraken each clear different parts of that combination.
How to use this in custody planning
SAFU should not change the 30% rule. Even with a $1B+ insurance fund, you do not want more than 30% of your stack on any CEX, because the fund covers platform-side incidents, not "platform decides to freeze your specific account for compliance reasons." Self-custody addresses both classes of risk; SAFU addresses only one.
Further reading: Proof of Reserves, Exchange evaluation handbook, CEX.