Binance’s Secure Asset Fund for Users, known as SAFU, has held more than $1 billion in reserve assets since it was seeded with 1,000 BTC in 2018. Most traders depositing six or seven figures onto the exchange have never read what the fund actually pays out for. That gap matters. Custodial risk doesn’t announce itself with a countdown clock, and the moment you need to know whether SAFU covers your specific loss scenario is exactly the moment you have no time left to research it. Regulators, insurers, and rival exchanges increasingly cite proof-of-reserves and insurance-fund structure as differentiators, but marketing language rarely matches contract terms. This explainer breaks down how SAFU is funded, what triggers a payout, where its coverage stops, and how Binance’s approach compares with the protection funds run by OKX and Bitget.
What the SAFU fund actually covers, and what it doesn’t
Binance created SAFU in July 2018 by allocating 1,000 BTC from its own balance sheet into a segregated reserve, then began adding a share of trading fee income over time, according to Binance’s official site. The purpose is narrow. SAFU exists to reimburse users when Binance itself determines a platform-level security incident caused losses, not to cover every category of harm a trader might experience.
In practice, the fund has been invoked for exchange-side breaches. When Binance disclosed a 2019 hot-wallet hack involving roughly 7,000 BTC, the company absorbed the loss through SAFU instead of socializing it across user balances or halting withdrawals indefinitely. That is the kind of event SAFU is built for: a security failure originating on Binance’s own infrastructure.
What it doesn’t cover is broader. Phishing attacks, malware that steals login credentials, SIM-swap attacks on your phone number, and transfers sent to the wrong address are treated as user-side failures, not SAFU-eligible events. A token collapsing in value or a rug pull on a listed asset also falls outside SAFU’s scope, since those are market outcomes rather than custody failures. Binance has never published a binding legal policy defining exact payout thresholds or timelines, so the fund works more like a discretionary reserve than a contractual insurance product.
Quick answer
- SAFU is Binance’s self-funded reserve for platform-level security breaches, not a government-backed deposit insurance scheme.
- It has covered incidents where Binance’s own infrastructure was hacked, including the 2019 hot-wallet breach.
- It does not cover phishing, credential theft, wrong-address transfers, or losses from token price movements.
- Best for traders who want documented proof of a backstop against exchange-side hacks, not a substitute for personal security habits like 2FA.
- Don’t treat the fund’s existence as a reason to skip due diligence on withdrawal habits and account security.
Evidence snapshot
The table below summarizes verifiable facts about SAFU, sourced from Binance’s own disclosures.
| Fact | Detail | Source / limit |
|---|---|---|
| Fund launch | Seeded with 1,000 BTC in July 2018 | Binance official site |
| Reserve size | Commonly cited at over $1 billion, per Binance’s own historical disclosures | Binance proof of reserves |
| Known payout event | Absorbed losses from a 2019 hot-wallet hack of roughly 7,000 BTC | Binance official site |
| Fee schedule context | Standard spot trading fee is 0.1%, a portion of which Binance has said supports SAFU over time | Binance trading fees |
| Audit status | No independently audited, real-time SAFU balance is published | Verification limit: figures reflect historical statements, not live audited data |
How SAFU compares to insurance and protection funds on OKX and Bitget
Binance isn’t alone in running a self-insured reserve. OKX operates its own risk reserve fund, and Bitget maintains a Protection Fund for derivatives users. Both are structured similarly: an exchange-controlled pool meant to absorb platform-side losses rather than deliver personalized deposit insurance. None of the three publish a continuously audited, itemized balance that updates in real time, so any claim about which fund is “bigger” relies on historical disclosures rather than current verified figures.
The practical difference worth weighing has less to do with fund size and more with track record and disclosure cadence. SAFU has a documented history stretching back to 2018 and a specific, publicly cited payout event. For a side-by-side look at how Binance’s broader security posture, fees, and account setup stack up against OKX, the Binance vs OKX comparison breaks down liquidity, proof-of-reserves practices, and beginner setup differences that sit alongside insurance-fund structure in a full risk assessment.
Fit / not-fit
Best for traders who want documented evidence that an exchange has both a reserve fund and a track record of using it, and who are comfortable treating SAFU as one input among several rather than a guarantee. It also suits users depositing meaningful balances who plan to pair it with strong account-level security, since SAFU explicitly excludes credential-theft scenarios.
Avoid if you’re looking for FDIC-style or SIPC-style protection with legally defined payout amounts and timelines. SAFU is discretionary and Binance-administered, not a regulated insurance product. Avoid it too if your primary risk concern is token-specific volatility or a project rug pull, since SAFU doesn’t address market losses. Traders in jurisdictions with limited legal recourse against Binance should weigh that alongside SAFU’s discretionary nature rather than relying on the fund alone.
SAFU’s track record: payouts, claims, and the pros and cons of self-insured custody
The clearest data point on SAFU’s real-world function is still the 2019 breach, when Binance confirmed a hacker withdrew roughly 7,000 BTC from a hot wallet and the company covered the loss through SAFU rather than through user account debits. Binance hasn’t published a running public log of every SAFU claim since, which limits how precisely traders can track the fund’s activity over time. For a broader view of how Binance frames its current fraud and security posture, the review of Binance’s AI-driven fraud detection claims examines a separate but related layer of the exchange’s security stack.
Pros
- Documented history of covering a large exchange-side hack without passing losses to users
- Reserve was seeded with a fixed, disclosed amount, 1,000 BTC, rather than an unverifiable promise
- Predates most competitor funds, giving it one of the longest track records among major exchange reserves
Cons
- No independently audited, continuously updated public balance
- Payout criteria are set at Binance’s discretion, not codified in a binding user contract
- Excludes the most common individual loss scenario: credential theft and phishing
Risk boundary
Cex101 is a comparison and education resource, not a source of personalized financial, legal, or tax advice. SAFU’s scope, funding level, and payout practices are set unilaterally by Binance and can change without advance notice to users. Verify fee schedules, invite benefits, KYC requirements, and product availability referenced in this article directly on Binance’s official site before you deposit funds or make a decision based on this information.
Verdict: when SAFU coverage should change your deposit decision
SAFU is a real, historically active reserve, not marketing vaporware, and it has one documented large-scale payout to point to. But it isn’t a substitute for account-level security. Before sizing a deposit around SAFU’s existence, confirm your own account is hardened: the 2FA setup guide walks through authenticator-app and hardware-key options that address the exact loss category SAFU excludes.
If you decide Binance’s combination of reserve fund, fee structure, and security stack fits your needs, signing up with the Invite Code CEX101 is worth doing at registration, since it is applied once at account creation and can lower your effective trading fee going forward rather than functioning as a one-time bonus. Register on Binance →. Availability, fee terms, and SAFU’s scope may change; see our terms and affiliate disclosure for details.
