Binance Has Spent Half Its SAFU Bitcoin, About $580 Million, Data Shows

Binance has spent about half of the bitcoin held in its emergency user-protection fund, according to on-chain data cited by CoinDesk on November 3. The wallet the exchange publishes as its Secure Asset Fund for Users, known as SAFU, held just over 7,500 bitcoin as of Tuesday, down from 15,000 bitcoin in February. At a price of roughly 77,000 dollars per coin, the remaining balance is worth about 580 million dollars.

The drawdown is the first time the fund has been tapped at anything like this scale, and it lands in the middle of the largest exchange theft on record. Binance has said the partial deployment of SAFU is one part of a 6.34 billion dollar package it set aside to cover losses from the October 29 hack, alongside its corporate treasury and a portion of its futures insurance fund. The exchange has pledged to restore SAFU to about 1 billion dollars, but it has given no date for doing so, and the gap between that promise and the fund’s own published top-up rule is now the question users and analysts are asking.

CoinDesk reported that four transactions on October 31 reduced the SAFU bitcoin balance by half. Blockchain data from mempool.space, cited in the report, shows the wallet Binance identifies as its SAFU reserve, at an address beginning 1BAuq7V, held 15,000 bitcoin after the fund was converted from stablecoins into bitcoin in February. The October 31 movements left it with slightly more than 7,500 bitcoin. A follow-up check by Unchained found that the bitcoin which left the fund on October 31 moved again on November 3, to a high-volume address without a public label, while the fund itself still held about 7,500 bitcoin, worth roughly 583 million dollars at that point.

What SAFU is and why Binance built it

SAFU stands for Secure Asset Fund for Users. Binance created it in July 2018, setting aside 10 percent of its trading fees into a separate reserve designed to cover user losses in extreme cases such as major security breaches. The name began as a joke: after an unscheduled maintenance period in 2018, founder Changpeng Zhao tweeted that funds were safe, and a creator known as Bizonacci turned the phrase into a viral video titled “Funds Are Safu.” Binance adopted the nickname and formalised it into a real fund the same year.

The fund was first called on in May 2019, when hackers stole more than 7,000 bitcoin, worth over 40 million dollars at the time, from Binance. SAFU covered the losses in full, and the episode became a central part of the exchange’s reputation for making users whole after security failures. For years afterwards the fund grew with trading revenue, passing 1 billion dollars, and was held largely in stablecoins for price stability. In early 2026 Binance converted the entire fund into bitcoin, completing the switch in February with 15,000 bitcoin, a move it framed as a long-term view of bitcoin as a transparent, auditable reserve asset.

The top-up rule that does not cover spending

Binance’s SAFU frequently asked questions page states that the exchange rebalances the fund back to 1 billion dollars if its value falls below 800 million dollars because of bitcoin price fluctuations. That wording is precise, and it is now the centre of attention. The fund has fallen below the 800 million dollar trigger, but not because bitcoin’s price fell. It fell because Binance spent half of it.

CoinDesk noted that the published rule does not cover the fund being spent. Binance has separately pledged to restore SAFU to about 1 billion dollars, but it has not said when, nor has it said how much of its futures insurance fund was used alongside SAFU, nor whether the SAFU spending sits inside the 6.34 billion dollars it set aside or alongside it. Those are not minor bookkeeping questions. They determine how much of the exchange’s own money has actually been committed, and how quickly the safety net will be rebuilt before any future incident tests it again.

What spending SAFU does and does not prove about solvency

It is tempting to read the halving of SAFU as a verdict on Binance’s finances, but the evidence points in a more complicated direction. Spending an emergency fund after an emergency is, on its face, what the fund exists for. The 2019 precedent, when SAFU covered a 40 million dollar theft in full, established exactly this use case. The difference this time is scale: the October 29 theft was roughly 150 times larger than the 2019 loss, and no single reserve, however large, was designed to absorb a 6.3 billion dollar hit on its own. That is why Binance combined SAFU with its corporate treasury and part of its futures insurance fund, and why the exchange has emphasised that the total package exceeds the estimated impact.

What the drawdown does show is the limit of a fixed-size reserve against a loss of this magnitude. Even before the hack, SAFU at roughly 1 billion dollars covered only about a sixth of the eventual 6.3 billion dollar impact. The fund was never sized to cover a theft of this size alone, and its deployment should be read as one leg of a larger funding effort rather than as the whole story. Analysts watching the exchange’s proof-of-reserves snapshots, which Binance has been publishing in phases since the hack, will be looking for the same picture from the other side: whether customer assets are fully backed after the replenishment, regardless of which internal pot paid for it.

What the drawdown does not prove, on its own, is insolvency or a shortfall in customer funds. Binance says users will not lose money, and the phased reopening of withdrawals supports that claim in practice: on November 1 the exchange processed 4.65 billion dollars of withdrawals in nine and a half hours against about 1.01 billion dollars of deposits, a net outflow of roughly 2.1 percent of assets, according to figures reported from the company’s briefing. Founder Changpeng Zhao noted that most of the net outflow came in the first couple of hours and that about 98 percent of customers chose to stay. A run on the exchange, the classic signal of a solvency crisis, did not materialise in that first window.

Why the bitcoin denomination changes the risk

Holding an emergency fund in bitcoin rather than stablecoins was a deliberate strategic choice, and it cuts both ways. On the upside, bitcoin is transparent and auditable on-chain, it carries no issuer or counterparty risk, and its price appreciation since February meant the fund was worth more than the roughly 1 billion dollars converted into it. Crypto Briefing reported in early October that the fund held about 1.27 billion dollars in bitcoin, including roughly 270 million dollars of unrealised profit, before the hack.

On the downside, a bitcoin-denominated reserve is worth less in exactly the circumstances when it may be needed most. Sharp market falls tend to coincide with industry crises, so a reserve that shrinks as bitcoin falls offers less protection at the moment of maximum stress. The fund’s own top-up rule acknowledges this by triggering a refill when price falls push it below 800 million dollars, but as noted, that rule was written for price moves, not for spending. The October 31 deployment has now exposed a gap in the rulebook: the fund can fall below its trigger through use, with no automatic refill obligation attached. Whether Binance revises the rule, or simply refills the fund voluntarily and quickly, will be a meaningful signal about how seriously it takes the gap.

What to watch next

For users, the practical takeaway is narrower than the headlines suggest. The SAFU deployment confirms that Binance is spending its own reserves, as promised, to cover the hack, and that the emergency fund did what it was built to do. It also confirms that the fund is now half its former size, with no published timetable for restoration, and that the rules governing its refill were not written for this scenario. Both halves of that picture are true at once, and both deserve to be kept in view as the recovery continues.

What is SAFU?

SAFU stands for Secure Asset Fund for Users, an emergency reserve Binance created in July 2018 by setting aside 10 percent of its trading fees. It is designed to cover user losses in extreme cases such as major security breaches, and it was first used in May 2019 to cover the theft of more than 7,000 bitcoin.

How much bitcoin is left in SAFU?

According to on-chain data cited by CoinDesk, the SAFU wallet held just over 7,500 bitcoin as of November 3, worth about 580 million dollars at roughly 77,000 dollars per coin. That is half the 15,000 bitcoin it held after Binance converted the fund from stablecoins in February 2026.

Has Binance said when SAFU will be refilled?

Binance has pledged to restore SAFU to about 1 billion dollars but has given no timeline. Its published rule requires a top-up only when the fund falls below 800 million dollars due to bitcoin price fluctuations, which does not cover the fund being spent.

Does spending SAFU mean Binance cannot cover user losses?

Not on the evidence available. Binance set aside 6.34 billion dollars from SAFU, its corporate treasury and part of its futures insurance fund, reported about 95 percent of affected assets replenished by November 2, and processed large withdrawal volumes after reopening without a run. The open questions concern the refill timetable and disclosure, not a demonstrated shortfall in customer funds.

Source: CoinDesk

Related reading on MM Crypto Analysis Web

• Binance Opens Second Withdrawal Phase as Deposits Overtake Outflows
• Bitcoin Braces for US Midterm Elections as History Warns of Sell-Offs
• Binance Hack Funds Spread Across 12,000 Wallets

More in Bitcoin on MM Crypto Analysis Web.