Two funds tested by one hack
After attackers drained the hot wallets of exchange Binance in the October 29 hack, the exchange reached for two funds of this kind. Its November 12 announcement says the more than $6.34 billion it committed came from “a partial deployment of the Secure Asset Fund for Users (SAFU),” part of its futures insurance fund “above the level required under Binance’s risk-management framework,” and its corporate treasury.
Binance also “committed to replenishing SAFU to return the fund to approximately US$1 billion.” The fund dates from July 2018, when Binance began setting aside 10% of all trading fees for it, according to a 2022 announcement that also lists its wallet addresses.
What the SAFU wallet showed on November 17
Anyone can read the bitcoin address Binance published for the fund. Block explorer mempool.space shows it received 15,000 BTC in five transfers between February 2 and February 12, 2026, then sent 7,500 BTC to a single address in two transactions on October 31. Binance hasn’t said what that transfer was for.
On the morning of November 17 it held 7,500.0014 BTC. At Coinbase’s spot price of $64,953.67 at 05:30 UTC, that comes to about $487 million. It is one of several addresses Binance listed for the fund, so it isn’t the fund’s whole balance.
How a derivatives fund works
The other kind sits behind futures trading. OKX, which calls its pool a Security Fund, says on its own page that when a liquidated position fills “lower than the account’s bankruptcy price, the resulting deficit (the excessive loss) is covered by the Security Fund.” Closing out at a better price leaves a surplus, which goes into the fund.
When a fund drops “significantly lower than a certain preset threshold,” auto-deleveraging starts. OKX describes it as closing out opposing positions that are in profit or heavily borrowed, matched against the bankrupt ones.
Where you see it
OKX publishes the balance through a public data feed that needs no account. At 05:27 UTC on November 17, 2026 the feed gave the fund’s total as $2,681,819,109.40, a field the API documentation defines as “the total balance of security fund, in USD,” with 99,117,440.86 USDT set against BTC-USDT perpetual swaps.
Traders also see an ADL indicator from 0 to 5 on each position, where 5 means “first in queue if the insurance fund is depleted.”
Not deposit insurance
The word “insurance” invites a misreading. OKX says its fund “is not an insurance policy, a custodial protection fund, or a guarantee against user losses,” and that it does not cover losses from “security breaches.” Binance chose to use its funds after a breach, which shows how much each exchange decides for itself.
Public schemes don’t step in either. The FDIC’s fact sheet of July 28, 2022 says its insurance “does not protect against the default, insolvency, or bankruptcy of any non-bank entity, including crypto custodians, exchanges, brokers, wallet providers, and neobanks.”
In the UK, the FCA says it is “highly unlikely” crypto users are covered by the Financial Services Compensation Scheme. Read your exchange’s terms for what its fund covers and whether it publishes the balance.