Circle gives 95 days to migrate from CCTP V1

Circle notified developers that burn limits for its Cross-Chain Transfer Protocol V1 will begin to fall on Oct. 31 and that the company will pause legacy USDC cross-chain contracts on Dec. 1. Any integration still pointing to V1 after the pause will no longer move USDC across chains.

A burn limit caps how much USDC can be destroyed on one blockchain so it can be reminted on another. Circle plans to reduce V1 burn limits through November and then pause the legacy contracts on Dec. 1. The company intends to keep enough minting capacity to complete outstanding attestations and to ensure users retain access to funds and pending redemptions during the phase-out.

Migrating from CCTP V1 to CCTP V2 requires code changes. V2 uses different contract addresses, interfaces and APIs that are not compatible with V1. Integrators must point to V2 versions of TokenMessenger, MessageTransmitter and TokenMinter, update contract interfaces, and change depositForBurn calls to the new function signature.

The V2 depositForBurn adds parameters for a permitted destination caller, a maximum fee and a minimum finality threshold. Attestation handling moves to a /v2/messages/{sourceDomainId} flow. Projects must also implement support for either standard or fast settlement where available and account for any applicable fees.

Circle’s supported-chain matrix lists 27 blockchains on the current CCTP network, but Aptos, Noble and Sui remain V1-only. Native routes to or from those chains still depend on the legacy contracts unless an integrator adopts a separately documented alternative. Circle did not disclose which exchanges, wallets, bridges or applications continue to call the old contracts.

In November 2025 Circle reported CCTP had processed more than $110 billion across about 5.3 million transfers, combining V1 and V2 activity through Nov. 14, 2025. Because burn limits begin to fall before the final pause, teams that need uninterrupted cross-chain service face reduced transfer capacity in November and a full stop to V1 transfers after Dec. 1.

Key technical tasks for developers are migrating contract addresses, updating interfaces and APIs, revising depositForBurn calls with the new parameters and switching to the /v2 attestation flow. Projects that do not complete these changes before capacity reductions may experience constrained throughput in November and halted USDC transfers after Dec. 1.