Bitget CEO Gracy Chen has publicly committed to replenishing the exchange's user protection fund within one week of her announcement, a pledge that follows a significant security incident and the phased restart of user withdrawals across the platform.

The timetable Chen set out is precise: the fund will be refilled within seven days. Protection funds of this kind serve as an exchange-level backstop designed to cover user losses in the event of a security breach or operational failure. As of this writing, however, the size of the balance that was drawn down, the source of capital for the refill, and any formal remediation plan have not been independently confirmed.

The commitment comes while Bitget is still restarting withdrawals asset by asset in the wake of the hack, with BTC withdrawals already reopened and ETH targeted for September 29. The sequenced rollout indicates the exchange continues to manage operational constraints tied to the underlying incident rather than having returned to full normal operations.

What the Pledge Does and Does Not Confirm

Chen's announcement establishes a deadline but stops short of disclosing the fund's current balance, its custody arrangement, or the mechanism by which users can verify the replenishment. A pledge to refill a fund is distinct from a verified, on-chain-auditable refill: the commitment cannot be confirmed until the exchange publishes proof of the deposit or a third-party auditor signs off. Until one of those proofs arrives, users have no independent benchmark for tracking whether the seven-day deadline is being met.

The triggering event was a hack in which $387.5 million in stolen assets was routed toward Bitcoin via THORChain, an episode that exposed the limits of voluntary blocking mechanisms at the protocol layer. On-chain investigators at AMLBot subsequently traced 4 BTC from the hack into Wasabi CoinJoin, a privacy-mixing protocol that complicates recovery efforts. Those parallel developments mean the fund refill is proceeding against a backdrop of active asset-recovery uncertainty.

What Would Substantiate the Commitment

Three developments after the one-week deadline would substantiate Chen's pledge: a public disclosure of the fund's replenished balance together with its wallet or on-chain address, an official explanation of the triggering event and which users or positions were affected, and confirmation that all withdrawal queues have cleared. Eligibility criteria for any claims process that may open would complete the picture. The absence of these details after the deadline would constitute an unmet pledge rather than partial progress; until they are made public, the fund's coverage and accessibility remain unquantified.

User Risk Checks and Counterparty Considerations

A refill pledge improves the optics of user protection, but it does not automatically translate into covered losses for affected parties. Users can verify their account balances and open positions against exchange records, monitor Bitget's official announcements for confirmed proof of the fund deposit, and check whether withdrawal restrictions on their specific assets have been fully lifted as the phased reopening continues.

The distinction between a public one-week pledge and a verified, liquid reserve matters for anyone evaluating counterparty risk. Exchange protection funds vary widely in their terms, custody structures, and claims processes, as reflected in published exchange fund frameworks across the industry, so the undisclosed terms of Bitget's own fund remain the key detail for users assessing their coverage. Until Bitget publishes a confirmed fund balance with on-chain verification or an independent attestation, the pledge remains a stated intention rather than a completed remediation.

The broader question for the exchange's user base is whether the refill represents a one-time remediation or the start of a restructured approach to reserve transparency. Exchanges that publish real-time proof-of-reserve attestations provide a structurally stronger guarantee than those relying on periodic CEO statements, and Bitget has not yet indicated which model it intends to adopt.

Source: DefiLiban