Community Trust ScoreVerified
Bitget topped its Protection Fund back above $300 million by September 30. The exchange did it two days ahead of the deadline it had set for itself after a security breach on September 24 hit the platform with a $388 million financial impact.
Why It Matters
The swift restoration of Bitget's Protection Fund highlights the exchange's commitment to user security and risk management in a volatile market landscape. In light of increasing cyber threats facing cryptocurrency platforms, timely actions like this can enhance user trust and confidence, potentially mitigating the broader impacts of security breaches on market stability. This proactive approach may also set a precedent for other exchanges, encouraging them to bolster their own security measures and risk management strategies.
The timeline here is pretty compressed. The breach landed on September 24. By September 28, Bitget had publicly committed to restoring the fund within a week. Then, on September 30 — two days early — the fund crossed back above $300 million. Customer balances, the exchange said, were never touched. The fund itself acts as a separate layer of protection, sitting apart from the reserves that back individual account balances. So the breach hit the fund, not the balances directly. That’s a meaningful distinction, and Bitget has been leaning on it hard in its public communications.
What Bitget hasn’t said: the exact amount of new capital it injected to get the fund back above $300 million. No details on that. The valuation is calculated using daily prices at midnight UTC, so the number shifts with the market, but the exchange hasn’t broken down how much fresh money came in versus how much was already sitting there.
Protection Fund Claims Process Still Applies
The fund’s restoration doesn’t mean users automatically get paid out. Bitget keeps the right to review every claim individually. Users whose accounts were compromised or who lost assets due to platform-wide events outside their control can file claims — but eligibility doesn’t guarantee compensation. The exchange evaluates each case based on its own findings. That assessment process didn’t go away just because the fund got replenished.
It’s a nuance that probably matters a lot to anyone who was directly affected. The fund exists, the money’s there, but the outcome of any individual claim still depends on what Bitget’s review turns up. Unclear how many claims have been filed so far. The exchange hasn’t said.
And the reserve picture looks solid, at least on paper. As of September 29, Bitget’s reserve ratio sat at 131% across 19 covered assets, with each individual asset holding above 100%. The snapshot was taken at 09:00 UTC on September 29.
Reserve Reports Carry Caveats
Worth being careful with that 131% number. These reserve reports aren’t audits. The PCAOB’s Office of the Investor Advocate put out an advisory in 2023 warning that proof-of-reserves reports can exclude liabilities or borrowed assets. So a 131% ratio looks strong, but it’s a snapshot, not a full accounting. Bitget itself acknowledges the reports aren’t comprehensive audits, even as it uses them to signal financial health.
That’s not unique to Bitget — it’s basically an industry-wide issue. Proof-of-reserves became a talking point across the crypto exchange space after 2022, but the methodology still varies widely and the limitations haven’t gone away.
Withdrawal Access Coming Back in Phases
Services weren’t all back at once. USDT withdrawals came online first, available on Ethereum, BSC, Solana, and Tron networks. Other cryptocurrencies, fiat, and peer-to-peer services were scheduled to resume on October 2 at 08:00 UTC. So as of the time of this writing, full withdrawal access was either just restored or in the process of being restored.
The phased approach makes sense from an operational standpoint — you don’t flip everything back on simultaneously after a breach this size. But it also means some users have been sitting on locked assets for over a week since the September 24 incident. That’s a long time, especially in a market that can move fast.
Bitget hasn’t specified which assets faced the longest delays or whether any users with specific cryptocurrency holdings faced timelines beyond October 2. No details on that front.
The breach itself — what caused it, how it happened, who was responsible — hasn’t been fully detailed publicly. The exchange has focused its communications on the fund restoration and the withdrawal schedule rather than the mechanics of the incident. That’s probably frustrating for users who want to know what actually went wrong before they decide whether to keep funds on the platform.
The fund page, at minimum, stays updated daily with a midnight UTC valuation. Bitget’s reserve ratio, as of September 29, sat at 131% across those 19 assets.
Frequently Asked Questions
How much did the security breach cost Bitget?
The security breach on September 24 resulted in a financial impact of $388 million on Bitget’s Protection Fund.
When did Bitget restore its Protection Fund above $300 million?
Bitget restored the Protection Fund to over $300 million by September 30, two days ahead of the deadline it committed to on September 28.
Does the Protection Fund guarantee compensation to affected users?
No. Bitget retains the right to evaluate each claim individually, and eligibility to file a claim does not guarantee compensation — outcomes depend on the exchange’s findings.





