Binance announced on Saturday that its USDC holdings are now fully backed following a significant cryptocurrency theft on Thursday. The exchange reported that it has replenished 90% of the affected assets, up from approximately 80% on Friday. This update comes as 823 million USDC tokens remain frozen, a move that researchers distinguish from funds actually returned to the exchange.
USDC's issuer, Circle Internet Group (NYSE:CRCL), possesses the ability to freeze the stablecoin via a blacklist mechanism, providing recovery teams with a containment tool. However, this does not automatically restore Binance's reserves or allow withdrawals to resume. The exchange's October 31 update measures replacement assets backing customer balances, while recovering the stolen coins is a separate process. Binance can acquire replacement USDC even as the frozen stolen tokens remain outside its control.
Containment Metrics and Comparisons
According to an investigation by Bitquery on October 31, the identified balance of 823 million USDC was frozen before it could be moved. The report also noted that 1.76 billion USDT tokens were locked, representing about 71% of the stolen USDT. Another 729 million USDT avoided freezing through swaps. These figures result in a containment-share gap of approximately 29 percentage points between USDC and USDT. It is important to note that this comparison covers only the traced incident balances and does not measure either issuer's general recovery rate or establish how quickly frozen funds can be returned.
Range's analysis on October 30 revealed that Circle's freeze occurred 24 minutes after USDC reached the collection wallet, while Tether froze USDT at that wallet 37 minutes after it arrived. Each interval starts when the respective token arrived, so the comparison uses separate starting points.
Backing vs. Recovery
Issuer backing is a distinct measure from recovery. Circle states that USDC reserves consist of cash and cash equivalents that support one-for-one dollar redemption. Binance's claim concerns its own holdings relative to customer balances. Neither measure establishes that the frozen tokens have returned to Binance.
Native cryptocurrencies lack an equivalent issuer switch. Bitquery's Saturday snapshot showed about 233.5 million stolen XRP unmoved in one wallet and 18,270 bitcoin unspent. These observations reflect tracked holdings at 16:51 UTC, not a confirmed liquidation schedule.
"Binance will absorb the financial impact of these stolen funds, not our users," co-CEOs Yi He and Richard Teng wrote on Friday. This pledge precedes Saturday's reserve update. The Associated Press reported on Friday that Binance had reserved more than $6.34 billion in company funds. Reserving funds and acquiring the specific replacement tokens are separate steps, and neither confirms that withdrawals have resumed.
Independent Estimates Differ
Independent estimates of the incident vary. TRM Labs tallied $6.36 billion, while Elliptic's estimate, updated Saturday at 05:00 UTC, stands at $6.43 billion—a gap of $70 million. The estimates differ in tracing coverage and valuation methods, so their denominators must remain separate.
Binance said it took a new reserve snapshot at 00:00 UTC Saturday. Its full cryptographic proof is still being generated, with completion estimated by November 3. The current backing claim thus comes before that verification milestone.
Risks remain: Reopening withdrawals depends on security checks, and the breach investigation is incomplete. Freezing tokens does not resolve their legal return or establish a recovery date. Illiquid replacement assets could also delay full replenishment. Binance aims to reopen withdrawals on Sunday, November 1, but Saturday's update gives no confirmed restart time. Will customers regain access before the full reserve proof is available?
