Coins: 518Source: Binance Spot24h Vol: 4.669B USDTBTC: 72.936K 1.3%ETH: 2.022K 1.5%Market feed
From the newsroom

Circle’s legacy USDC transfer routes approach December shutdown

Circle’s CCTP V1 wind-down timetable calls for reduced capacity during November and a December 1 contract pause, requiring applications to adopt separate V2 integrations.

Prepared with AI assistance. Thumbnail is an AI-generated editorial illustration. Sources and supporting documents are listed below.

Cartoon blockchain engineer guides a stablecoin onto a new bridge beside a retired cross-chain transfer route.

Applications still using Circle’s original Cross-Chain Transfer Protocol face a narrowing window to move to its replacement. The company’s published timetable starts the CCTP V1 wind-down on October 31 and schedules a pause of the legacy contracts for December 1, 2026.

The change concerns the infrastructure applications use to transfer USDC between blockchains. It does not announce the retirement of USDC itself. For wallets, bridges and other services built around V1, however, the transition requires changes beneath the user interface.

A staged reduction in capacity

Circle plans to lower legacy burn limits over the phase-out period, progressively reducing the amount of USDC that can enter new transfers. CCTP’s model burns tokens on the originating chain and enables corresponding tokens to be minted at the destination after an attestation.

That process makes the treatment of transfers already under way especially important. Circle’s migration guidance says pending redemptions will remain available during the wind-down and that minting allowances will be kept above pending attestations before the full pause.

The assurance relates to the transition period. Developers still need to reconcile outstanding transfers and follow the applicable chain-specific instructions. The published timetable does not provide a universal promise that every old route will remain usable until the final day.

V2 requires a new integration

CCTP V2 uses different contracts and APIs and is not backward compatible with V1. An application therefore needs to update its routing and transaction logic, rather than simply rename a setting.

The newer version supports standard and faster transfer modes, along with hooks that can trigger actions after funds reach the destination. Those capabilities create additional options for application builders, but they also require testing against the replacement interfaces and supported networks.

From a user’s perspective, a familiar wallet screen can hide a substantial change in how a transfer is processed. A service needs to track the source transaction, the attestation and the destination mint, and make failures or delays understandable to the person sending funds.

The deadline to watch

Circle announced the broader move away from V1 in November 2025 and published the October-to-December schedule in August 2026. The current milestone is the planned December 1 pause, after which integrations still pointing at the affected legacy contracts are expected to stop transferring USDC between chains.

The published schedule establishes the intended wind-down. It does not provide observed transfer capacity for every network on November 7. Integrators need the current migration documentation and route status to determine what remains available, particularly for networks with separate transition arrangements.

Sources & further reading

Evidence used by our editorial team.

  1. Circle — CCTP V1 deprecation timetable and V2 transition
  2. Circle developer documentation — V1-to-V2 migration and pending redemptions
  3. CryptoSlate — legacy transfer-capacity phase-out, October 30, 2026
CircleUSDCInteroperabilityInfrastructure

Reader discussion (0)

Share your experience or add useful context. Submissions are reviewed before publication.

Join the conversation with a reader account.

No published comments yet.