Binance says it used part of its futures insurance fund to help replace cryptocurrency stolen in a reported $6.3 billion hack. But without a breakdown of contributions, remaining balances and required minimums for the affected pools, traders cannot tell what the transfer means for those funds’ ability to absorb losses.
- Binance named SAFU, futures insurance funds and corporate treasury as funding sources.
- Swolecharts tracked about $1.85 billion across the Binance insurance funds it monitored on November 1.
- Snapshots show a lower BTCUSDT balance, but not how much was used for recovery.
- A lower balance alone does not mean auto-deleveraging is more likely.
Three funding sources, no breakdown
In a reported update published October 31, 2026, Binance said it would use part of its Secure Asset Fund for Users (SAFU), a portion of its futures insurance fund and corporate treasury to replace assets stolen in a breach reported on October 29. Reports have valued the breach at $6.3 billion, but the available information does not clarify exactly what that figure measures.
Binance said the amount taken from its futures fund was above its required protection level. It also said it monitors coverage against historical stress scenarios and adds company funds when needed. The update did not say how much each source contributed, which pools supplied funds or what minimum balances Binance requires in the affected pools.
The reserves serve different purposes. SAFU is an emergency fund for incidents such as security breaches. Futures insurance funds cover certain shortfalls when a leveraged position is liquidated but still leaves a deficit. Corporate treasury is a separate source of company funds. Naming all three does not reveal how much risk any one fund now carries.
What the public balances show
Swolecharts listed approximately $1.85 billion across the Binance insurance funds it tracked at 09:00 UTC on November 1, down 24.96% over the previous 24 hours. That figure is the tracker’s aggregate, not a single pool available to every futures contract.
The tracker listed 649.67 million USDT and 199.98 million USDC for its BTCUSDT shared group, which covers BTC, ETH and BNB USDT-margined futures alongside other contracts. It also listed 273.32 million USDT and 100 million USDC for a SOLUSDT shared group, and 80.33 million USDT for an AAVEUSDT pool. These are examples, not a full breakdown of every fund.
For comparison, FeeØtter reported official API readings for the BTCUSDT fund at 00:00 UTC on October 17: 791, 125, 863 USDT and 499, 980, 384 USDC. Together, those amounts total 1, 291, 106, 247 stablecoin units. The later rounded figures total 849.65 million, a difference of approximately 441.46 million units, or 34.2% of the earlier total.
The comparison does not record the recovery transfer. The snapshots are from different dates, and the available information does not show that they cover precisely the same contracts or account for every change in the fund. Ordinary liquidation activity, reallocations and other movements may also affect balances. Blaming the entire difference on the hack would be guesswork dressed up as arithmetic.
The exchange-wide total also does not show how funds are shared across contract groups. The listed pool figures provide a more specific snapshot, but Binance has not shared the pool-by-pool accounting needed to establish what was transferred, what remains available to each group or whether funds can move between them.
Why insurance funds matter to futures traders
In leveraged futures trading, a position can lose more than the margin supporting it. If that margin falls below the maintenance requirement, the minimum needed to keep the position open, the exchange begins liquidation. If a position cannot be closed at or above its bankruptcy price, the point where the trader’s margin runs out, a shortfall can remain.
A futures insurance fund is designed to absorb certain shortfalls. It does not reimburse traders for ordinary market losses, and it is separate from SAFU and customer deposits.
If the relevant fund cannot take over a bankrupt position, Binance’s rules allow auto-deleveraging, or ADL. The mechanism can reduce or close profitable positions on the opposing side to contain a deficit. That can force a winning trade to close, which is not a welcome surprise, even if the mechanism helps prevent losses from spreading further.
Binance’s fund guidance describes sizing based on a 99.9% confidence interval and historical stress scenarios. That figure does not guarantee that ADL will be avoided in 99.9% of liquidations. Binance’s guidance explicitly distinguishes the two. The reported recovery update does not include the stress-test calculations or pool-level minimums needed to assess the transfer’s effect.
Fund size is only one part of derivatives risk. Binance says its ADL risk measure also considers factors such as position concentration, order-book depth, volatility, average leverage, unrealised profit and loss, and margin utilisation. A lower reported balance alone does not show that ADL has become more likely. The relevant market conditions and Binance’s calculations for the affected pools are not public in the recovery update.
The distinction matters in practice. FTI Consulting reported more than $19 billion in crypto liquidations over roughly 24 hours during the separate October 10, 2025 market shock, and described how thin liquidity, leverage and ADL can interact under stress. That episode offers context on derivatives risk, but it does not establish whether Binance’s funds remain adequate after the transfer.
Recovery progress and the proof-of-reserves question
Binance said Bitcoin withdrawals resumed on November 1, with the first recovery phase covering selected assets across 15 networks. It also said 95% of affected assets had been replenished. The company did not specify whether that percentage refers to value, asset count or another measure, and it did not identify the futures fund’s contribution.
Binance said it took a customer reserve snapshot at 00:00 UTC on October 31 and expected a full zero-knowledge proof to take approximately 40-50 hours to generate, with the proof expected to be available by November 3 UTC. Such a proof can help verify claims about a specified dataset without revealing all the underlying information. But a customer reserve proof does not, by itself, provide a pool-by-pool accounting of futures insurance funds or a complete assessment of an exchange’s liabilities.
Binance’s reported assurance that the futures-fund contribution was above its required protection level may be accurate. Without more detail, users have little way to test that claim independently. The most useful disclosure would show how much each source contributed, the affected pools’ minimum balances before and after the transfer, and any later top-ups or reallocations. Loss estimates and withdrawal timelines remain difficult to verify without that kind of evidence.
Key questions and answers
-
Did Binance use its futures insurance fund to help replace stolen assets?
Binance’s reported October 31 update named a portion of the futures fund alongside SAFU and corporate treasury. It did not disclose how much came from each source.
-
How much remains across the funds tracked by Swolecharts?
The tracker listed approximately $1.85 billion across the Binance insurance funds it monitored at 09:00 UTC on November 1. That aggregate does not show the balance available to every contract.
-
Does the BTCUSDT snapshot comparison show how much Binance used?
No. The October 17 and November 1 figures differ by about 441.46 million stablecoin units, but the snapshots do not separate the recovery transfer from other fund activity.
-
Does a lower fund balance mean ADL is more likely?
Not on its own. Liquidity, leverage, concentration, volatility and other conditions matter. Binance has not published enough pool-level data to quantify any change in ADL risk.
-
Can customer proof of reserves verify the futures insurance funds?
Not by itself. Customer reserve disclosures and futures-fund records cover different things. A customer proof does not provide the missing pool-by-pool accounting.
