Bitget said on Sept. 30 that it had restored its Protection Fund to more than $300 million, following the financial impact of the security breach reported on Sept. 24.
The exchange said the incident created an approximately $388 million impact for the fund. At the same time, Bitget maintained that customer balances remained accurate and unaffected.
The restoration fulfills a commitment Bitget made on Sept. 28 to return the Protection Fund to at least $300 million within one week. The exchange said it completed that replenishment two days ahead of that deadline.
Bitget's announcement does not disclose how much new capital was contributed to restore the fund. The exchange also notes that the valuation displayed on its fund page is calculated using prices recorded at midnight UTC each day.
The distinction between Bitget's reserves and its Protection Fund is important.
Bitget describes customer reserves as backing covered account balances, while the Protection Fund operates as an additional financial safeguard for certain incidents involving customer assets.
According to Bitget's published conditions, users can submit claims when accounts are compromised or when assets are stolen or lost through platform-wide events that are not attributable to the user's own actions or trading behavior.
However, submitting a claim does not automatically establish that a particular loss will be reimbursed.
Bitget retains the ability to investigate affected accounts and assets and assess individual claims based on its findings. The restoration of the fund therefore represents a replenishment of the backstop, rather than confirmation that all potential claims have already been paid.
Bitget's separate reserve report shows an overall reserve ratio of 131% across 19 covered assets, with each asset listed above 100%.
That snapshot was taken at 09:00 UTC on Sept. 29, shortly before the exchange announced the Protection Fund restoration.
Proof-of-reserves data, however, has limitations. A 2023 advisory from the PCAOB's Office of the Investor Advocate noted that proof-of-reserves reports are not audits and can omit liabilities or borrowed assets. Such reports also cannot guarantee that assets will remain available at a later date.
That distinction becomes particularly relevant when evaluating an exchange's financial safeguards after a security incident. Reserve figures and a protection fund address different parts of the risk framework and should not be treated as interchangeable measures.
The Protection Fund restoration is also separate from Bitget's withdrawal-reopening schedule.
In its Sept. 30 service notice, Bitget said USDT withdrawals had reopened on Ethereum, BSC, Solana and Tron.
Other cryptocurrencies, fiat services and peer-to-peer services are following a separate timetable. Bitget's incident schedule lists the remaining services for Oct. 2 at 08:00 UTC.
This means restoration of the financial backstop and restoration of full platform functionality are two different milestones.
For customers waiting for specific assets or services to become available, the withdrawal timetable remains the relevant operational milestone.
From a risk-management perspective, the announcement provides two separate pieces of information.
First, Bitget says it has replenished the Protection Fund beyond the $300 million level after absorbing the reported $388 million impact. Second, the exchange has not indicated that every potential claim has been resolved.
The claims process remains dependent on Bitget's assessment of individual accounts, assets and circumstances. As a result, the existence of a replenished fund does not by itself establish the outcome of every affected user's claim.
The same distinction applies to reserves. A reserve ratio above 100% provides a snapshot of reported asset coverage, but it does not eliminate the broader operational, custody and platform risks associated with a centralized exchange.
The episode highlights why centralized crypto exchanges maintain multiple layers of financial protection.
Customer reserves are designed to correspond with covered customer balances, while a protection fund can provide an additional pool for qualifying incidents. The two mechanisms serve different purposes within an exchange's risk framework.
For users and market observers, the more significant question now moves beyond the headline figure of $300 million. Attention is likely to remain on how Bitget handles eligible claims, how quickly remaining services return, and what additional information becomes available about the Sept. 24 incident.
The exchange's reported fund restoration marks one step in that process. The reopening of withdrawals and the handling of individual claims remain separate stages.
Bitget says it has rebuilt its Protection Fund to more than $300 million after absorbing approximately $388 million from the Sept. 24 security incident. Customer balances and the fund are treated separately, while claims remain subject to assessment and investigation. Meanwhile, withdrawal access is returning according to a separate asset and network schedule, with additional services expected to reopen on Oct. 2.
The information published by CryptosNewss is for informational, analytical, and educational purposes only. Digital assets are highly volatile and speculative. Neither CryptosNewss nor its contributing journalists provide personalized financial, investment, legal, or tax advice. Readers must conduct independent due diligence and consult licensed financial advisors before executing capital allocations.
Financial Intelligence Desk
CryptosNewss market analysts and on-chain intelligence specialists.
