Circle Sets December 1 Cutoff for Legacy USDC Transfers

CCTP V1 faces a December 1 pause

Circle’s August 27 migration notice says the change is mandatory for applications that still use legacy contracts. It describes a month of declining capacity before the general pause stops those integrations transferring USDC across chains.

The schedule is an earlier announcement reaching its implementation window, rather than a newly disclosed emergency shutdown. The reviewed notice does not publish each intermediate burn limit or a network-by-network record proving which reductions have already been applied.

The limits govern how much USDC can be destroyed on a source chain to initiate a transfer. A lower allowance means the old route has less capacity even before its final closure. That creates a practical distinction between an application remaining online and its chosen transfer route remaining usable.

Circle’s current CCTP product page explains the native burn-and-mint model: tokens are removed from one network and issued on another. It also says the legacy version will receive neither additional chain integrations nor feature updates.

The deadline concerns infrastructure for moving USDC, rather than a blanket end to the stablecoin. Circle’s separate USDC issuance arrangements under MiCA address the issuer and regulatory structure; the CCTP change concerns the route an application uses between networks.

USDC apps need separate V2 integrations

Circle first designated V2 the canonical version in its November 2025 transition announcement. That post described more than $110 billion in cumulative transfers and 5.3 million transactions across both versions as of November 14, 2025, not current usage or a measure of funds exposed to the cutoff.

The original announcement listed 17 V2 networks, compared with 27 in the August update. It also described an earlier phase-out timetable. For the present deadline, the later August notice and current migration documentation both specify October 31 through December 1.

V2 adds fast transfers and programmable actions after funds arrive. Those capabilities broaden what apps can do with a transfer, but the newer system cannot simply accept an unchanged V1 integration.

The developer migration guide identifies different contract addresses, changed contract interfaces and new offchain endpoints. Developers must also account for transfer-speed selection and variable fees on Fast Transfer transactions.

That makes the remaining work broader than changing a version label. A wallet can display the same USDC balance while its transfer service needs different instructions to move it. Migration readiness depends on the complete route, including the destination mint and the service retrieving Circle’s transfer confirmation.

Circle says pending redemptions remain available during the phase-out and that minting allowances will exceed pending attestations, allowing redemptions to finish before the contracts pause. That is the provider’s stated transition design, not independent confirmation that every pending transfer has settled.

The same operational distinction runs through Circle’s USDC distribution and redemption economics: holding a token, moving it between chains and redeeming it through an issuer are separate functions. A working balance display does not establish that each remains available through the same provider.

Noble USDC has a January 12 deadline

Noble is the exception requiring a separate timetable. Circle’s September 10 support notice says the network will not receive CCTP V2. It scheduled the end of new Circle Mint issuance there for October 13.

Existing Noble USDC remains transferable until the January 12, 2027 pause. Circle Mint redemptions remain available until that date, when Circle plans to pause the USDC contract and all CCTP routes on Noble.

Circle lists supporting centralized exchanges, a decentralized swap on Noble and remaining CCTP V1 routes as possible exits. After December 1, however, CCTP exits may be limited to destinations that still support legacy burns. A later Noble deadline therefore does not guarantee unchanged cross-chain access throughout December.

Circle plans to snapshot remaining balances on January 12 and begin manual redemptions January 13. Eligibility requires a holder-controlled wallet in that snapshot and satisfaction of compliance and security requirements. The notice does not promise automatic reimbursement to every address or unchanged liquidity at every exit venue.

Alternative.me’s Fear & Greed Index read 34, or Fear, on November 1, compared with 30 a day earlier. It measures broader Bitcoin sentiment, not the proportion of USDC applications ready for migration.

The next milestones are the general December 1 pause and Noble’s January closure. The reviewed sources do not establish how many integrations still rely on V1, their remaining transfer volume or the precise daily capacity reductions during November.