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

Introduction: where the four letters came from

On July 3, 2018, Binance published a post on its official blog announcing the creation of SAFU (Secure Asset Fund for Users). The announcement read: "To protect the future interests of all users, Binance will create a Secure Asset Fund for Users (SAFU). Starting from 2018/07/14, we will allocate 10% of all trading fees received into SAFU to offer protection to our users and their funds in extreme cases. This fund will be stored in a separate cold wallet." Two details there are worth holding onto: the allocation did not begin on the day of the announcement but eleven days later, on July 14; and this went out as a company announcement, not as a piece under CZ's byline.

That was a first in crypto. Before it, the standard way an exchange dealt with a disaster was to absorb it alone, and to close the doors and disappear when it could not (the Mt.Gox pattern). SAFU was the first time the industry turned emergency protection for users from a verbal promise into a pool of money on chain that could be checked.

The four letters later became a piece of crypto subculture. Every time an exchange runs into trouble or a project blows up, the community posts "SAFU?" as a question. Whether the exchange in question has something like SAFU, and whether the address can be looked up, decides where that day's questioning stops.

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, not held by a third-party custodian, not backed by any government. Which means the credibility of SAFU equals Binance's willingness to keep its promise. FTX, back in its day, also showed an insurance fund balance on its derivatives platform, but that number did not correspond to a separately segregated pot of money with an address you could look up — and when things went wrong, not a single coin came out of it. That is the difference between having an address you can verify and being asked to take someone's word for it.

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: SAFU is no longer a set of wallets spread across several chains. It is one address.

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 the address:

This table was checked word by word against that announcement in September 2026. If you come across the claim, which circulates elsewhere, that SAFU holds four cold wallets on four chains, go by the official announcement — that is not the current position.

How to verify it (30 seconds):

1. Open Etherscan.
2. Paste the address above into the search box.
3. Look at the USDC token balance of that address — note that it is the token balance, not the ETH balance.
4. Look at "Transactions" / "Token Transfers" — the whole history of money in and out of this address is there.

What to watch for: the history of this address should be mostly top-ups and rebalancing to maintain its 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

I have rewritten this section. The lists of SAFU payouts that circulate online — including the earlier version of this piece — mix in events where SAFU was never drawn on at all. With the definition tightened up, the number of times SAFU demonstrably covered a loss, with an official announcement to check it against, is one:

The next two events are often counted as SAFU payouts. By the official wording, neither is:

There was one more item I had written here in the earlier version, about a user being compensated by SAFU in July 2024 after a third-party approval exploit. Going back through it line by line this time, I could not find any verifiable public source for it, so it has been removed. Better one entry fewer than one entry nobody can check.

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

IV. SAFU vs FDIC: four fundamental 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

In the situations below, SAFU explicitly does not pay:

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, SAFU does not pay. The reason is that this does not count as the platform being attacked.
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 is classified as the user's own security responsibility, and SAFU does not pay.
5. An event of extreme size (an $8 billion FTX-scale hole, say). The SAFU pool is about $1 billion, and cannot cover an event five to ten times that size in full.

The short version: SAFU covers losses from attacks at the level of the Binance system itself, and only up to the size of the SAFU pool.

VI. Similar mechanisms at other exchanges

This version of the table deliberately gives no specific amounts for any of them. The few figures in the earlier version (Kraken at "roughly $100 million (estimated)" and the like) were ones I could not trace to a public source when I went back through them, and the word "estimated" in particular has no business being on this site — so I would rather leave a blank than leave a number nobody can look up. If you do want to compare amounts, go to each exchange's own disclosure page and read what it says that day.

Which means what this table can really compare is not the amounts but whether you can verify them. In that column there is only one exchange that puts the address out and lets anyone go and check it on chain; the rest either have the company's own account of it or do not even have an address. That does not mean the money is not there at the others. It only means you have no way of confirming it yourself — and by the standard this archive works to, being able to confirm something yourself and being asked to believe it are two different things.

The practical conclusion on SAFU is that it is a key indicator of whether an exchange can take a hit and stay standing, but it is not an absolute backstop. Your decision path should run like this: look at PoR first (the warning before anything goes wrong), then at SAFU or a similar insurance arrangement (the buffer afterwards), and at the same time tier your own holdings so that no single vector being broken costs you everything.

One of the reasons I use Binance myself is that, among this group, its insurance fund is the only one I can check on chain for myself. SAFU cannot protect me completely, but it can materially reduce the loss in events below the FTX scale. It is a necessary-but-not-sufficient extra buffer.