SAFU Explained: The Address, the Size, How Many Times It Has Actually Been Used, and the Gap With FDIC

SAFU (Secure Asset Fund for Users) was set up by Binance in July 2018. According to the official SAFU FAQ, Binance allocated a percentage of trading fees to grow the fund, and its purpose is to protect users and their funds in extreme cases.

Before it, an exchange that ran into a disaster mostly absorbed it alone, and went into bankruptcy proceedings when it could not. What SAFU did was put emergency protection for users into a pool of money whose address is public and can be checked on chain.

Where the four letters of "SAFU" came from is set out in the official FAQ: during an unscheduled maintenance, CZ tweeted that "Funds are safe"; in 2018 a content creator called Bizonacci put the line into a YouTube video titled "Funds Are Safu", which spread quickly and became a meme. Binance later backronymed it into the fund's formal name, Secure Asset Fund for Users.

I. What SAFU actually is

SAFU is a separate pool of money in a wallet, with stated rules about where the funds come from, what they are for, and when they can be used:

There is one detail here that is easy to miss: SAFU is a fund Binance set up voluntarily, and Binance decides how it is used. It is not required by law and not backed by any government; the fund is now held and managed by Nest Clearing and Custody Limited under ADGM regulation, but whether it pays and how much it pays remain Binance's own decisions — the official wording is that Binance retains full discretion. In other words, the addresses and balances are something you can verify yourself; the payout step is something you can only watch it do when the time comes.

II. On-chain verification: checking the SAFU balance yourself

This is the one part of this piece you can verify with your own hands, so let me get the terms right first: per the official SAFU FAQ as updated in February 2026, what Binance lists is two addresses — one Bitcoin address and one USDC address on Ethereum; per the Binance Academy entry (updated October 13, 2026), the fund is now held entirely in Bitcoin, so the Bitcoin address is the main one to check.

Two layers need keeping apart here. On April 18, 2024, Binance published Update: SAFU Conversion to USDC on its official blog. The post states that the fund's assets were converted 100% to USDC, that the size is held at the $1 billion order of magnitude (the original wording is "this level is typically set at $1B"), and it gives that USDC address. That is where things stood at the time. The SAFU FAQ in Binance's official help centre was then updated on February 2, 2026, Binance Academy now says the fund has been moved entirely into Bitcoin, and the current position is no longer the one in that blog post:

If you come across the claim, which circulates elsewhere, that SAFU holds four cold wallets on four chains, that claim is not the current position — go by the addresses Binance publishes.

How to verify it:

1. The USDC address. The help-centre FAQ still lists it. Open Etherscan, paste the address into the search box, and look at the USDC token balance — note that it is the token balance, not the ETH balance. With the fund held entirely in Bitcoin, this is not where the main balance sits.
2. The Bitcoin address. Open any Bitcoin block explorer, paste the address in, and look at the balance and the transaction history — there is no token layer on a Bitcoin address, so what you are reading is the BTC balance itself.
3. On both, look at "Transactions" / "Token Transfers" — the whole history of money in and out of these two addresses is on chain.

Two things to keep in mind. First, with the fund now held entirely in Bitcoin, the Bitcoin balance is what mainly tells you the size of the fund; read only the USDC address and you will badly undercount. Second, the dollar value of bitcoin moves with the coin price, so the total you work out on the day will not sit exactly on the "approximately US$1 billion" Binance states — the FAQ says as much itself, and adds that the fund is rebalanced if it falls below US$800 million. Binance's October 31, 2026 notice also said it expected a partial deployment of SAFU and committed to bringing the fund back to about US$1 billion, so the balance may sit well below that figure; go by what the chain shows.

What to watch for: the history of these two addresses should be mostly top-ups and rebalancing to maintain the size, not a steady outflow. Large unusual outflows with no matching announcement from the company are the signal to be wary of.

III. How many times SAFU has actually been used

SAFU was used once in 2019, with an official announcement to check it against; in October 2026 Binance said it would partially deploy the fund again, and the amount has not been published:

The next event is often put down to SAFU. By the official wording, it was not:

Beyond that, the movements in the SAFU balance have been top-ups and rebalancing to maintain its size — the conversion of the entire fund to USDC in April 2024 and into Bitcoin in early 2026, for example. All of that is visible on chain, but it is internal management, not a payout.

IV. SAFU vs FDIC: five differences

Plenty of people describe SAFU as the FDIC of the crypto world. That analogy does harm, because the two are fundamentally different on two points: who stands behind it, and who decides to trigger it.

So the accurate description of SAFU is this: an emergency reserve Binance set up voluntarily, aimed at hacks of moderate size, which is not backed by any government and is not an absolute backstop. The biggest gap between it and FDIC is not size; it is the fundamental difference in how it is triggered and what it covers.

V. What SAFU does not cover

First, the right way to put this. The official FAQ only says what SAFU's coverage "may include"; it publishes no list of exclusions, and it leaves the question of which losses and which claims are eligible entirely to Binance's discretion. So the accurate description of the situations below is not that SAFU "explicitly does not pay", but that Binance has made no promise to cover them:

1. The exchange misusing user funds itself. This is the FTX scenario — and if Binance itself ever had a problem on the FTX scale, SAFU could not cover it either (and Binance controls whether it is triggered). PoR and SAFU deal with the two stages either side of a disaster and cannot stand in for one another: PoR is the warning before, SAFU is the buffer after.
2. The user being phished. If you signed an approval on a third-party phishing site, had Permit2 abused, or had your clipboard hijacked, and funds left your Binance account as a result, that loss is not among the ones Binance has written down. The reason is that it is not a vulnerability or deficiency in Binance's own systems or security protocols.
3. Liquidation caused by a large market move. A user's derivatives position being liquidated is outside SAFU's scope (that is market risk).
4. A stolen password or a broken 2FA. This one depends on the cause. What the FAQ says SAFU's coverage may include is precisely a compromise of login credentials resulting from a vulnerability or other deficiency in Binance's systems or security protocols; if the credentials leaked on the user's side, that is the user's own security responsibility and Binance has made no promise to cover it. Whether a given case qualifies is at Binance's discretion.
5. An event of extreme size (an $8 billion FTX-scale hole, say). The SAFU pool is roughly US$1 billion and moves with the market; it cannot cover an event five to ten times that size in full.

The short version: what Binance says SAFU may cover are losses caused by something going wrong in Binance's own systems or security protocols; whether it pays, and how much, is its own decision, and the amount is bounded by the size of the pool. Claims go through Binance Support and should be made within 90 days of the loss.