The two completely different types of "insurance fund" in crypto, what triggers a real payout, which exchanges have the largest reserves, and why the fund balance number is less important than the payout record. This is mechanics education — not a recommendation to trade on any specific platform.
Two types of fund — don't mix them up
Here's where most traders get confused. When someone says "insurance fund," they could mean one of two completely different things. Mixing them up is the fastest way to misunderstand how safe your money actually is.
Type 1: Derivatives Insurance Fund. This is a reserve pool attached to the futures market. It fills up from liquidation fees and leftover margin every time a trader gets force-closed. It pays out when a liquidated position goes negative — meaning the trader lost more than their margin — and covers the shortfall so the counterparty doesn't lose money. Every futures exchange has one of these. It affects you directly if you trade perpetuals.
Type 2: User Protection Fund. This is a separate reserve — like Binance's SAFU — that covers security breaches, hacks, and platform-side failures. It's funded by trading fee allocations or direct exchange contributions. It pays out when the exchange itself loses your money through a hack or system compromise. It has nothing to do with your trading positions.
| Feature | Derivatives Insurance Fund | User Protection Fund |
|---|---|---|
| What it covers | Negative balances from liquidation | Hacks, security breaches, system failures |
| How it fills | Liquidation fees + leftover margin | Fee allocation or exchange capital |
| When it pays | Every time a position goes underwater | Only after a qualifying security event |
| Affects your trades? | Yes — directly, every session | No — only if the exchange gets hacked |
| Published balance? | Yes, usually updated daily | Sometimes — varies by exchange |
For the rest of this article, "insurance fund" means the derivatives fund — the one that affects your futures positions every time you open a trade.
The derivatives insurance fund: how it fills and when it drains
The mechanics are straightforward once you see the flow. Every time a trader gets liquidated, money moves through a specific sequence:
Step 1: The position hits the maintenance margin threshold. The liquidation engine takes over and starts closing the position.
Step 2: The position is closed at the bankruptcy price (where equity hits zero) or better. If the fill price is better than bankruptcy — meaning the engine got a price that leaves some equity remaining — the leftover margin gets routed into the insurance fund.
Step 3: On top of that, exchanges charge a specific liquidation fee. On Binance, it's called the Liquidation Clearance Fee (1.25% of notional for BTCUSDT). On OKX, there's a liquidation fee plus a Deleveraging Fee. On Gate, it's a flat 0.075% built into the bankruptcy formula. These fees flow into the fund.
Step 4: When a liquidation goes bad — the position's losses exceed the remaining margin, creating a negative balance — the insurance fund covers the shortfall.
The insurance fund is not a safety net for your losses. It's a mechanism that prevents one trader's catastrophic liquidation from becoming someone else's loss. When you hear "the insurance fund covered it," that means the fund paid to keep the counterparty whole — not the liquidated trader.
On Gate.io, the flow is particularly transparent: remaining maintenance margin after a liquidation goes into the fund as an inflow, liquidation profits go in as another inflow, and losses from handling liquidation orders are the sole outflow. Gate publishes this as a running ledger on their insurance fund page.
Fund balances across major exchanges (2026 data)
Here's what the numbers look like as of October 2026. These are the derivatives insurance funds and user protection funds, separated — because conflating them is the most common mistake in this space.
| Exchange | User Protection Fund | Derivatives Insurance Fund | Verifiable? |
|---|---|---|---|
| Binance | SAFU: ~15,000 BTC (~$1B), replenishment floor $800M | Multiple pools; no consolidated figure published | SAFU wallet address on-chain |
| OKX | Risk Shield (~$700M reported) | Documented; current balance not independently verified | zk-STARK proof of reserves |
| Bybit | Not disclosed separately | ~$400M (mid-2026), daily balance history published | Yes — daily historical balance page |
| MEXC | Guardian Fund: $100M (target $500M by 2028) | 751M USDT (Aug 2026) | Fund wallet addresses published |
| Bitget | Protection Fund: $309M (post-hack rebuild, Sept 2026) | Not separately disclosed | Reserve ratio: 131% (Sept 29, 2026) |
| Gate | Not disclosed | Published with inflow/outflow ledger | Insurance fund page with running balance |
A few things stand out. Binance's SAFU is the largest single disclosed fund at roughly $1 billion — but it converted entirely to BTC in early 2026, so its dollar value now fluctuates with Bitcoin's price. The $800 million replenishment floor means Binance has committed to topping it up if BTC drops enough.
Bybit is the most transparent on the derivatives side: daily balance updates for the ~$400M insurance fund, publicly accessible and historically traceable. That matters because a fund balance is a snapshot — what you really want to see is the trajectory.
Bitget's protection fund went from $464 million to $309 million in a single week — absorbing the $387.5 million hack on September 24, 2026. That's the kind of stress test that tells you whether a fund is real or just a marketing number. The fund fired, it paid, and users didn't lose money. The rebuild to $309M with company capital was completed within a week.
Real payout history: when the funds actually fired
A fund balance means nothing without a documented payout record. Here's what has actually happened:
| Event | Exchange | Amount | Which fund | Outcome |
|---|---|---|---|---|
| Binance hack (May 2019) | Binance | ~$40M (7,000 BTC) | SAFU | Fully covered, zero user losses |
| Bybit hack (Feb 2025) | Bybit | ~$1.46B (ETH cold wallet) | Emergency loans + treasury (not protection fund) | Withdrawals paused briefly; users made whole |
| Bitget hack (Sept 2026) | Bitget | ~$387.5M | User Protection Fund ($464M → $309M) | Users unaffected; fund absorbed full loss |
| Binance Oct 2025 crash | Binance | $283M (depegged assets) | Exchange compensation (not SAFU) | Compensated USDe, BNSOL, wBETH holders |
| BitMEX closure (Sept 2026) | BitMEX | ~$270M fund | Insurance fund disposition undisclosed | Exchange shut down; fund fate unknown |
Look, here's what the data actually shows. The two largest hacks covered by dedicated funds — Binance 2019 and Bitget 2026 — both resulted in zero user losses. That's the fund doing exactly what it's supposed to do.
But the Bybit $1.46 billion hack in February 2025 was not covered by any protection fund. Bybit used emergency loans and treasury reserves. If Bybit hadn't had the balance sheet to cover that, users would have been exposed. The fund structure mattered less than the parent company's financial health.
And BitMEX's ~$270 million insurance fund? When the exchange closed in September 2026, nobody publicly disclosed where that money went. That's the risk of an undisclosed disposition — a fund only protects you if it's actually deployed in your favor.
What happens when the fund runs dry
This is the scenario nobody wants to think about, but it's built into every exchange's rulebook. When the insurance fund can't cover a negative balance, the next line of defense is auto-deleveraging (ADL).
ADL works like this: the exchange identifies traders on the opposite side of the market who are profitable. It then partially closes their positions — at the bankruptcy price of the liquidated trader — to offset the loss. You didn't place a close order. You didn't choose to take profit. The system did it for you, because the fund ran out.
If you're holding a profitable perpetual position and the insurance fund gets depleted, your position can be partially closed without your consent. This isn't theoretical — it happens regularly on high-volatility days. Check your ADL ranking on your exchange (usually displayed next to your position). Higher-ranked positions — those with more profit and higher leverage — get ADL'd first.
On Binance, there's an additional layer: negative balances are automatically reset to zero every ten minutes. So even in the worst case, you won't owe the exchange money after a liquidation. But "not owing money" and "not losing money" are very different things — your margin is still gone, and the ADL mechanism means other traders absorb the residual risk.
The practical implication: a healthy insurance fund doesn't just protect liquidated traders. It protects profitable traders from having their positions involuntarily reduced. The fund is a buffer between you and ADL.
How to evaluate a fund before you trade
Here's a practical framework. Fund size is the weakest signal — it's the easiest number to publish and the hardest to verify. Four stronger signals, in order of reliability:
1. Published wallet address or daily balance page. If you can read the balance yourself on-chain or on a daily-updated page, that's verifiable. Binance SAFU's BTC wallet is public. Bybit publishes daily fund history. These are checkable.
2. Documented payout precedent. Has the fund actually fired? Binance (2019) and Bitget (2026) have proven their protection funds work. An exchange with a large fund but zero payout history is untested.
3. Independent audit of reserves. Hacken audits MEXC's monthly reserves. Bybit's proof of reserves is Hacken-verified. An audit doesn't guarantee safety, but unaudited numbers are just claims.
4. Scope clarity. Read the published terms. MEXC's Guardian Fund covers "platform system compromise and critical technical failure" — that's narrow and specific. Vague language like "extreme cases" (Binance SAFU's description) gives the exchange wide discretion about when to deploy.
| Evaluation signal | Strong | Weak |
|---|---|---|
| Balance verification | On-chain wallet or daily published balance | Single press release number |
| Payout history | Documented past payouts | No recorded payouts (untested) |
| Audit status | Monthly independent audit (e.g., Hacken) | Self-reported snapshot |
| Scope definition | Specific triggers listed in published terms | Vague "extreme cases" language |
The uncomfortable truth: no insurance fund covers phishing, SIM swaps, account takeovers, or your own trading losses. The fund exists to keep the exchange's futures market solvent when individual traders blow up. It's a system-level backstop, not personal insurance.
Ready to start trading?
Open a free account on OKX →