dYdX Votes on Shifting USDC Backing From Noble to Injective

The dYdX Foundation has opened an on-chain vote on a v9.9 upgrade that would move USD Coin (USDC) backing on dYdX Chain from Noble to Injective, ahead of Circle's scheduled pause of its Noble USDC contract. Voting closes Nov. 16, and if the proposal passes, the upgrade is expected to complete around Nov. 18.

The deadline driving the migration is firm. Circle has set Jan. 12, 2027 as the date it will pause its Noble USDC contract and shut down CCTP V1 routes into and out of Noble. For dYdX Chain, which relies on Noble-issued USDC as its backing asset, that date is an operational cliff: without an alternative rails provider, deposits and withdrawals denominated in the stablecoin would stop functioning.

What does the v9.9 upgrade actually change?

The proposal adds a Canonical USDC module to dYdX Chain and gradually replaces Noble-issued USDC with Injective-issued USDC as the backing asset. Two parameters stay fixed throughout: the on-chain token identifier does not change, and user balances do not change. From the holder's perspective, the migration is meant to be invisible at the balance level while the plumbing underneath is swapped.

The operational rules tighten once migration begins:

• Users would be able to deposit USDC through Injective alone.
• Deposits originating on Noble, including CCTP transfers routed through the network, would be refused and returned to the sender.
• Withdrawals could be directed to Noble or Injective, but not to other chains.
• Ending withdrawals to Noble, once the Noble-backed portion of the supply is cleared, would require a separate governance approval.

That last point matters for practitioners. Noble does not disappear from the withdrawal path on day one; it is wound down deliberately, and only a governance vote removes it. Market makers and treasury operators running automated deposit flows should re-point their rails to Injective before the cutover, since Noble-routed CCTP deposits will bounce rather than land.

A built-in safety brake on backing

The upgrade also encodes an automatic safeguard. If USDC on dYdX Chain is not fully backed during the transition, deposits and withdrawals would pause automatically while trading continues. In practice, that separates the settlement layer from the market layer: positions remain tradable, but stablecoin inflows and outflows halt until full backing is restored. The design choice limits silent under-collateralization of the stable asset during the swap from one issuer rail to another.

The Cosmos Hub community pool is moving too

A separate migration addresses a related exposure. The Cosmos Hub community pool holds 566,067.055810 USDC.n, and voters have already approved moving that balance to Injective. The figure is modest by treasury standards, but the vote signals that the shift away from Noble is not confined to a single chain; it is a broader reallocation of Cosmos-ecosystem USDC custody ahead of Circle's January 2027 cutoff.

What does this change for dYdX users?

For traders and infrastructure operators, the practical consequences are narrow but concrete. Balances and token identifiers remain intact, so no user action is required to preserve holdings. Deposit routing, however, becomes Injective-only once migration begins, and any workflow built on Noble CCTP deposits must be reconfigured or it will fail. Withdrawal destinations narrow to Noble and Injective, excluding direct exits to other chains.

For the dYdX chain itself, the vote secures continuity of its primary settlement asset past Circle's Jan. 12, 2027 pause date. If the proposal fails, the chain would face a compressed window to design and approve an alternative before the Noble contract goes dark.

The vote closes Nov. 16, with the upgrade targeted for completion around Nov. 18 if approved, leaving roughly fourteen months between the migration's finish and Circle's deadline.