Skip to content
Blockchain Posts

infrastructure

Circle starts CCTP V1 legacy deprecation Oct 31; Noble USDC fully paused Jan 12

Circle begins ramping down CCTP V1 burn limits on Oct 31, with full V1 contract pause on Dec 1. Noble's USDC and CCTP routes stay on a longer timeline, ending in a Jan 12 manual-redemption cutover.

by 5 min read
infrastructurecircleusdccctpnoble

Circle has pulled the trigger on the long-signaled deprecation of CCTP V1 Legacy, the first-generation Cross-Chain Transfer Protocol routing contracts that burn-and-mint USDC between chains. Two timelines are now live: a general one for every chain where CCTP V2 is available, and a longer Noble-specific one that ends in a hard pause of USDC and CCTP on Noble on Jan 12, 2027.

What happened

Circle published two deprecation notices in late October:

  • Migrate to CCTP V2 ahead of CCTP V1 legacy deprecation — the general path.
  • Circle is discontinuing support for USDC and CCTP V1 on Noble — the chain-specific path.

Both go into effect Oct 31. The general-path dates:

  • Oct 31, 2026 — V1 burn limits begin dropping. Transfer throughput tapers over roughly one month, trending toward zero.
  • Dec 1, 2026 — V1 contracts are paused. Any integration still calling V1 methods on supported chains stops transferring USDC crosschain. Any pending V1 transfers in flight before this date are expected to complete.

Circle characterizes migration to CCTP V2 as "required, not just recommended." V2 is live on 27 blockchains; the full list is in Circle's docs.

Noble is a separate story

Noble, the Cosmos-based USDC issuance chain, is not receiving CCTP V2 and is being wound down as a USDC venue:

  • Oct 13, 2026 — minting new USDC to Noble via Circle Mint was already disabled. Redemptions remain available.
  • Oct 31, 2026 — Noble's CCTP V1 burn limits begin reducing in step with the general schedule.
  • Dec 1, 2026 — Noble CCTP exits may be limited to V1-supporting destination chains.
  • Jan 12, 2027 — Noble USDC contract and CCTP routes are fully paused. Circle Mint redemptions end. A snapshot of all Noble USDC balances is taken.
  • Jan 13, 2027 — a manual redemption process begins, backed by that snapshot.

Migration paths Circle lists for Noble USDC holders:

  1. Send to a centralized exchange that supports Noble USDC and withdraw to a supported chain.
  2. DEX swap on Noble to a stablecoin that will continue to live there.
  3. CCTP V1 burn to another supported chain while the route still works.

Circle will publish an exit-venue shortlist. It is not running its own exit UI — the burden sits with holders and the venues they trust.

Numbers block

  • ~1 month of ramp between the Oct 31 start of reduced V1 burn limits and the Dec 1 full V1 pause (general path).
  • ~2 months between Oct 31 and the Jan 12 full Noble pause (Noble path).
  • 27 blockchains on CCTP V2.
  • $92M USDC on Noble — cited by CryptoSlate and Forkast, not confirmed in Circle's own notice. Treat as single-sourced.

Mechanism — why burn-and-mint has versions

CCTP's "V1" and "V2" are not marketing versions; they are different contract sets with different fast-finality assumptions and different message-attestation flows. V2's main differences:

  • Fast transfers underwritten against pre-attested messages for a dedicated fee, instead of waiting for the full source-chain finality window.
  • Hooks: destination-side callbacks that let a smart contract act on the newly-minted USDC in the same transaction, enabling composable "receive-and-swap" patterns.
  • Chain-set differences: V2 omits some chains V1 supported (Noble, in particular) and adds newer rollups and alt-L1s.

Projects integrated against V1 call different method signatures and expect different message formats, so the migration is not a config change — it requires code and audit cycles. That is why Circle has been signaling the deprecation on each per-chain developer channel for most of the year.

Impact

  • Integrators that still route USDC through CCTP V1 on supported chains have until Dec 1 to migrate or risk broken flows (relayers, bridges, aggregators, treasury movers).
  • Noble USDC holders — mostly Cosmos-ecosystem users, Osmosis liquidity providers, and some crosschain treasuries — have a longer, more complex path. The Jan 12 manual-redemption cutover means the asset becomes procedurally illiquid once the contract pauses, and liquidity has to be re-aggregated by Circle on a snapshot basis.
  • CEX dependency rises: Circle's "send it to a supported exchange" path makes exchanges the de facto bridge of last resort for Noble USDC balances.

What to watch

  1. Which venues publish support for Noble USDC exits before Jan 12. Circle has said it will link a shortlist; its appearance is the trigger for most Cosmos LPs.
  2. DEX-side liquidity on Noble between now and Dec 1. Thin exit books will push users to CCTP V1 burns to Ethereum or Solana while the route still functions.
  3. Integrator migration announcements from the top CCTP V1 integrators — bridge aggregators (LI.FI, Socket), DEX routers, and treasury movers.
  4. Whether any further Noble-adjacent chains (Elys, Dydx, Celestia-connected rollups) get the same deprecation treatment.

Context — the stablecoin issuer's cleanup phase

CCTP V1 shipped in 2023, barely two years ago. Its deprecation is a signal that Circle is now at the stage of lifecycle work that only mature financial infrastructure gets to: pruning first-generation routing in favor of a protocol it can underwrite with faster finality. The parallel pruning of Noble is a sharper decision: by not shipping V2 there, Circle is effectively consolidating USDC onto the chains where it has either direct Mint presence or a V2 contract. For Cosmos as an ecosystem, this makes IBC USDC the only path forward, with CEX-mediated exits as the fallback for existing balances.

Sources

Related stories