Initia USDC Bridge Reserve Hit $63 in Oct. 23 Hack

Initia’s USDC bridge reserve collapsed to just $63 during the October 23 hack, on-chain analytics firm Bitquery found, while the same data revealed 55 ordinary withdrawal attempts failed as the protocol came under attack.

The two figures, a near-zero reserve balance and a count of blocked user withdrawals, represent the clearest on-chain record yet of how the October 23 incident affected Initia’s USDC bridge at the moment of impact, according to CryptoSlate’s reporting citing Bitquery’s analysis. Bitquery’s data captures a snapshot of the bridge’s liquidity state during the attack window, not a final loss tally; the reserve figure reflects how far the pool was drained before the measurement was taken. For related coverage, see AFX Cross-Chain Bridge on Arbitrum Hit by Attack, $24.15M USDC Stolen.

Bitquery Finds Initia’s USDC Bridge Reserve at $63 During the Hack

A USDC bridge reserve of $63, per Bitquery’s on-chain read, is functionally empty for a cross-chain facility that routes stablecoin liquidity between networks. The figure indicates the reserve was drained to a residual balance during the active phase of the October 23 incident, leaving the bridge unable to process outbound USDC transfers at scale. Bitquery attributed this observation to on-chain state at the time of the hack, not to a post-incident audit or an official Initia disclosure. For related coverage, see Top Stablecoin Issuers in 2026: Reserve Model, Distribution, and Market Role Compared.

The incident sits within a broader pattern of cross-chain bridge exploits that have repeatedly exposed reserve shortfalls at the moment of attack. The AFX cross-chain bridge on Arbitrum was hit for $24.15 million in USDC earlier in 2026, illustrating how bridge reserves concentrated in a single stablecoin become a high-value target once an attacker gains access to withdrawal logic. In Initia’s case, the $63 endpoint suggests near-total drainage occurred before monitoring systems flagged the event. For related coverage, see Bybit and Circle Forge Strategic Partnership to Advance Global USDC Adoption.

Bitquery’s role here is that of an on-chain data indexer reading contract state, not an investigative body with attribution authority. The firm observed the reserve level; it did not identify the exploit vector, the attacker’s wallet, or the total value extracted. Those details, as of the available reporting, remain unconfirmed. For related coverage, see India's Largest Exchange Denies Hack After $16M Outflows.

55 Ordinary Withdrawal Attempts Failed, According to the Data

Alongside the reserve reading, Bitquery counted 55 failed ordinary withdrawals during the same period. The qualifier “ordinary” matters: it distinguishes standard user-initiated redemption requests from any privileged or admin-level calls that may have moved funds during the same window. Fifty-five failed attempts signals that users were actively trying to withdraw USDC through the bridge as the reserve was being depleted, and that those requests were rejected because the reserve balance was insufficient to settle them.

A failed withdrawal count of 55 does not translate directly to a user-loss figure. Each failed attempt may represent a different notional amount, and it is unknown from the available data whether those users later recovered funds through alternative routes or protocol remediation. What the count confirms is that the reserve depletion created real, measurable friction for users attempting to access their assets during the incident window.

The Initia blockchain itself was halted during the broader attack. As reported separately, a hacker printed $2.7 million in crypto as Initia’s blockchain was brought to a stop, placing the USDC bridge drain within a multi-vector incident rather than an isolated bridge exploit. The $63 reserve figure and the 55 failed withdrawals represent the USDC-specific dimension of that event.

What the Reported Bridge Data Shows, and What It Does Not

Bitquery’s two reported data points, the $63 reserve balance and the 55 failed ordinary withdrawals, are distinct observations that measure different things. The reserve balance is a liquidity state reading: it shows how much USDC remained in the bridge contract at the time of measurement. The failed withdrawal count is a transaction outcome reading: it shows how many user-initiated requests the contract rejected. Neither figure is a total loss estimate.

Confirmed observations

Per the Bitquery analysis cited by CryptoSlate: the USDC bridge reserve reached $63 during the October 23 hack, and 55 ordinary withdrawal attempts failed during that window. Both figures are attributed to on-chain data indexed by Bitquery. No official Initia statement confirming or disputing these figures was included in the available reporting.

Unanswered questions

The exploit mechanism, the identity or wallet address of the attacker, the total USDC value drained from the bridge, and the current recovery or reimbursement status of affected users are not established by the available evidence. The $63 endpoint tells analysts when the reserve was effectively exhausted; it does not tell them how much was in the reserve before the attack began, which would be necessary to calculate total drainage. Any figure purporting to show total losses from the USDC bridge specifically should be treated as unconfirmed unless sourced to a primary disclosure from Initia or a verified on-chain accounting.

Why Bridge Reserve Monitoring Matters During an Incident

Cross-chain bridges hold reserves of wrapped or native assets to settle outbound transfer requests from users moving funds between networks. When a reserve is depleted, whether through an exploit, a bank-run dynamic, or a combination of both, the bridge cannot honor pending withdrawals even if the underlying protocol remains operational. A reserve reading of $63 in a USDC bridge effectively communicates insolvency at the contract level at that moment in time.

Reserve balance as a real-time incident indicator

On-chain indexers like Bitquery can surface reserve depletion in near-real-time by monitoring contract state, making reserve balance a leading indicator during an active attack rather than a lagging one. A reserve that drops from millions to double digits within a single block range signals that outflows are not ordinary user redemptions but an extraction event. For protocol monitors and white-hat responders, this signal type is what triggers emergency pause mechanisms, though the value of that signal depends entirely on how quickly it is acted upon.

Failed withdrawals as a secondary stress indicator

Withdrawal failure counts complement reserve readings by confirming that user demand existed at the same time liquidity disappeared. If a reserve drains with zero concurrent failed withdrawals, the more likely explanation is an authorized administrative action or a slow withdrawal queue. Fifty-five failed ordinary withdrawals coinciding with a near-zero reserve balance is a pattern consistent with a hostile extraction event that outpaced organic user redemption. USDC’s role as the dominant stablecoin on many cross-chain routes, as tracked across protocols via DeFiLlama’s stablecoin dashboard, means bridge reserves denominated in USDC are among the highest-value single-asset targets in DeFi infrastructure. The broader implications for stablecoin reserve models are examined in Coincu’s comparison of top stablecoin issuers in 2026.

FAQ: Initia USDC Bridge Reserve and Failed Withdrawals

What did Bitquery find about Initia’s USDC bridge reserve? Bitquery’s on-chain analysis found the USDC bridge reserve reached $63 during the October 23 hack, per CryptoSlate’s reporting. This figure represents the reserve balance at a measured point during the incident, not a final audit result.

How many ordinary withdrawals failed? Bitquery counted 55 failed ordinary withdrawal attempts during the same window. The qualifier “ordinary” distinguishes these from any privileged protocol calls. The dollar value of each failed withdrawal is not confirmed in the available reporting.

What is confirmed versus unconfirmed from the available information? Confirmed: the $63 reserve reading and the 55 failed ordinary withdrawal count, both attributed to Bitquery’s on-chain data. Unconfirmed: total USDC stolen from the bridge specifically, the exploit method, attacker identity, and the current reimbursement status for the 55 affected withdrawal attempts.

What is the next concrete trigger to watch? An official Initia post-mortem disclosing total bridge losses, the exploit vector, and a reimbursement timeline would resolve the key open questions. Separately, any resumption of USDC bridge activity on Initia with a replenished reserve would confirm that the protocol has addressed the liquidity gap the Bitquery data identified. Until either of those disclosures occurs, the $63 figure and 55 failed withdrawal count represent the most granular on-chain evidence available for the October 23 event.