Bitget said on Sept. 30 it had rebuilt its Protection Fund to more than $300 million after the fund absorbed approximately $388 million in losses from the Sept. 24 security breach. The exchange says customer balances were unaffected, with the fund operating as a backstop rather than the primary reserve layer backing accounts. Bitget met a Sept. 28 pledge to restore the fund to the $300 million threshold within a week, completing the replenishment two days after that commitment, though the release does not quantify the new capital contributed.
Why it matters
The $388 million absorbed by the Protection Fund is one of the larger self-insured exchange losses disclosed publicly. Bitget's fund sits separately from the reserves that back customer account balances, which the exchange pegged at a 131% ratio across 19 covered assets in a snapshot taken at 09:00 UTC on Sept. 29. That ratio is a static read: a 2023 advisory from the PCAOB's Office of the Investor Advocate noted that proof-of-reserves reports are not audits, can omit liabilities or borrowed assets, and offer no assurance of asset availability after the snapshot date.
The fund itself is not a blanket insurance policy. Under Bitget's published conditions, users may submit claims when accounts are compromised or assets are lost through platform-wide events not attributable to their own actions. The exchange retains discretion over claim assessment, and eligibility does not guarantee reimbursement of a particular loss.
Market impact
USDT withdrawals opened on Sept. 30 across Ethereum, BSC, Solana, and Tron. Bitget's incident timetable puts the remaining cryptocurrencies, fiat, and peer-to-peer services back online on Oct. 2 at 08:00 UTC, a separate milestone from the fund restoration. The combination of a $300 million-plus backstop and a 131% reserve print is the case Bitget is making to institutional clients and retail users still waiting on full access, though both figures carry the caveats that reserve snapshots and self-administered insurance funds always carry.
Frequently asked questions
-
What is Bitget's Protection Fund and how is it different from reserves?
Bitget's Protection Fund is a self-managed backstop for users whose accounts are compromised or who lose assets through platform-wide events not attributable to their own actions. Reserves, separately, are the assets that back customer account balances and were reported at a 131% ratio across 19 covered assets in a…
-
How much did the Sept. 24 security breach cost the Protection Fund?
Bitget said the fund absorbed approximately $388 million in impact from the Sept. 24 incident, one of the larger self-insured exchange losses disclosed publicly. The exchange pledged Sept. 28 to restore the fund to at least $300 million within a week and completed the replenishment two days later.
-
Were customer balances affected by the Bitget security breach?
Bitget says customer balances remained accurate and unaffected, with the fund absorbing the impact rather than user accounts being drawn down. The exchange's separate reserve report showed a 131% ratio across 19 covered assets in a Sept. 29 snapshot.
-
When can Bitget users withdraw their funds after the breach?
USDT withdrawals reopened Sept. 30 on Ethereum, BSC, Solana, and Tron. The exchange's incident timetable puts the remaining cryptocurrencies, fiat, and peer-to-peer services back online on Oct. 2 at 08:00 UTC.
-
Are Bitget's proof-of-reserves figures audited?
No. A 2023 advisory from the PCAOB's Office of the Investor Advocate noted that proof-of-reserves reports are not audits, may omit liabilities or borrowed assets, and offer no assurance of asset availability after the snapshot date.
CryptoSlate