Circle is scheduled to disable new USDC minting to the Noble blockchain through Circle Mint on 13 October 2026, beginning the operational phase of a migration that shifts the Cosmos ecosystem toward native USDC issued on Injective. The cutoff does not freeze Noble balances and does not end redemptions on that date. Circle says Noble redemptions through Circle Mint remain available until 12 January 2027, subject to the staged retirement of legacy cross-chain routes.

The issuer announced the timetable on 10 September. Circle said it is discontinuing USDC and Cross-Chain Transfer Protocol version 1 on Noble as it standardises around CCTP V2; Noble will not receive the newer protocol. Native USDC and CCTP are already live on Injective, where Circle identifies the token’s mainnet contract and offers Circle Mint access to eligible institutional customers.

What changes on 13 October

The immediate change is narrow but important. Circle Mint customers will no longer be able to create new USDC directly on Noble after 12 October. Existing USDC on Noble remains transferable, and eligible customers can continue redeeming it through Circle Mint during the transition period.

Circle’s later deadlines carry greater operational risk. CCTP V1 burn limits from Noble are due to start declining on 31 October. After 1 December, exit routes may be limited to destination chains that still accept CCTP V1 burns. On 12 January 2027, Circle plans to pause Noble access through both Circle Mint and CCTP. A manual redemption process is scheduled to begin the next day for qualifying balances captured in Circle’s pause-date snapshot.

That manual route has conditions. Circle says the USDC must be in a holder-controlled wallet included in the snapshot, and the holder must satisfy compliance and security requirements. USDC left inside liquidity pools or smart contracts may not qualify for the same process. Users and protocols therefore need to follow the instructions of their own wallet, exchange or application rather than assume every balance can be moved through an identical path.

Why Injective is central to the replacement

Injective said guided migration opened through Skip:Go on 11 September, allowing supported users to move from Noble USDC, commonly displayed as USDC.n, to Injective-issued USDC, displayed as USDC.inj. Supported networks named at launch included Cosmos Hub, Osmosis, dYdX, Neutron, Terra 2.0, Initia, XPLA and ZIGChain.

The architecture changes the issuance point. Injective becomes the Circle issuance network, while Inter-Blockchain Communication carries that USDC to participating Cosmos chains. Injective also supports CCTP V2 connections to networks including Ethereum, Base and Solana. The intended benefit is less fragmentation between competing representations of USDC, but that benefit depends on wallets, exchanges, applications and liquidity providers completing their own integrations.

dYdX is expected to adopt USDC.inj as its sole eligible trading collateral on dYdX Chain. Injective’s announcement said existing dYdX balances and trading were unchanged at publication and that dYdX would provide its own timing and instructions. That distinction matters: a network-wide direction does not mean every venue has completed its migration or that users should move collateral without venue-specific guidance.

What the deadline does—and does not—prove

The minting cutoff confirms Circle’s planned withdrawal from new Noble issuance. It does not prove that liquidity has already consolidated on Injective, that all protocol positions have migrated safely, or that the change creates direct demand for INJ. USDC usage can increase on an underlying network without producing equivalent value accrual for the network’s native token.

The transition also introduces execution risk. Liquidity may be split across USDC.n and USDC.inj during the changeover. Applications can display similar tickers for assets with different contracts and transfer paths. Users face smart-contract, bridge, routing and counterparty risks, while protocols must update token lists, oracles, deposit controls and user interfaces without confusing legacy and replacement assets.

NetNapz assessment

Base case: 13 October is an infrastructure milestone rather than a market shock. New institutional issuance to Noble stops, while redemptions and ordinary transfers continue. The more consequential test comes after 31 October, when CCTP V1 burn limits begin tightening and liquidity incentives increasingly favour the Injective-issued version.

Bull case: exchanges, wallets and major Cosmos applications adopt USDC.inj cleanly, liquidity consolidates without material disruption, and CCTP V2 expands efficient access between Cosmos and larger USDC markets. Evidence would include growing USDC.inj balances, broad venue support and reduced reliance on legacy Noble routes.

Bear case: fragmented integrations leave users navigating incompatible tickers and routes, liquidity remains divided, or protocol-held Noble balances become difficult to exit as legacy limits fall. Confirmation would come from delayed venue migrations, widening swap discounts, paused deposits or emergency governance actions.

The thesis is invalidated if Circle changes the timetable or if operational data show that the migration has not progressed beyond announced support. The key horizon runs from the 13 October minting cutoff through the 31 October burn-limit reduction, the 1 December route contraction and the 12 January 2027 pause.

Sources and next checks

• Circle: discontinuing USDC and CCTP V1 support on Noble — 10 September 2026.
• Injective: USDC migration across Cosmos and dYdX — 10 September 2026.
• Circle: native USDC and CCTP on Injective — 7 May 2026.

NetNapz will watch for Circle status changes, venue-specific dYdX instructions, reductions in Noble CCTP limits and evidence that liquidity has actually shifted. This report describes protocol and issuer changes, not personal financial advice.