Bitget: Withdrawals Set to Resume in Phases Starting September 28, Vulnerability Fixed Bitget said the vulnerability involved in its September 24 security incident has been identified and fixed, with withdrawals set to resume in phases after security checks are completed. The schedule is as follows, all at 08:00 UTC: BTC on September 28, ETH on September 29, USDT on September 30, and other tokens, fiat and P2P services on October 2. Bitget said user account balances remain unaffected and its Protection Fund will cover the financial impact of the incident. Trading and deposits remain operational, while Mandiant and SlowMist continue to assist with the investigation.

When withdrawals are queued, how do lenders get paid? On cSigma Atlas, Pool Managers can fulfill pending requests in two ways: -> By returning capital from underlying investments, allowing queued withdrawals to be processed automatically. -> By using available reserve liquidity to fulfill requests in First-In, First-Out (FIFO) order. This is the liquidity infrastructure tokenized asset managers need- and cSigma ‘s infrastructure is bringing it onchain. Designed to keep withdrawals fair, transparent, and capital-efficient for lenders.

Bitget Reopens ETH Withdrawals, Records Healthy Inflows @Bitget finally reopened $ETH withdrawals on September 29 after a period of restricted access. The protocol recently confirmed about 651 $ETH in net inflows, with 9,674 $ETH sent in and 9,023 $ETH withdrawn as of 09:00 UTC. The restoration process was completed after $BTC withdrawals reopened on September 28.

UPDATE: @Bitget reopens $ETH withdrawals, reporting a net inflow of 651 ETH in the first hour, as the exchange continues its phased restart following last week's $387.5M hack. $USDT withdrawals scheduled for September 30.

Bitget: All Withdrawals to Face Independent Checks Bitget says it is tightening its security controls following the recent breach. Access to highly sensitive systems has been restructured, with critical operations requiring multiple approvals, while withdrawal requests will undergo independent verification. The exchange also said affected third-party security functions will remain disabled until remediation is complete, and all internal credentials have been revoked and reissued.

Bitget CEO: Why Withdrawals Were Paused and Restored in Phases Bitget CEO Gracy Chen @GracyBitget said during a September 28 livestream that the security incident affected the exchange’s withdrawal infrastructure across multiple chains and assets. As a result, each chain had to undergo a series of security checks before withdrawals could resume, requiring the platform to restore withdrawals in phases. She said the suspension was a security measure and was not related to the sufficiency of user assets, with the related losses fully covered by the Bitget Protection Fund. Bitget restored BTC withdrawals first because the BTC withdrawal pipeline was the first to be ready and had not been affected by the attack, meaning it did not require the same level of comprehensive security verification. ETH and USDT withdrawals were restored later based on the progress of security checks and user demand.