Starting today, October 31, 2026, Circle begins cutting the burn limits on its legacy CCTP V1 contracts — the first mechanical step in a deprecation that ends when those contracts are paused on December 1, 2026. The change is scheduled, not sudden: Circle’s migration notice has carried the timeline since August 27. The number that matters today is 31 — the days left between this first limit reduction and the point where any integration still pointed at V1 stops moving USDC cross-chain.
Circle has framed the move as a hard requirement rather than a suggestion. “Migration from CCTP V1 (Legacy) to CCTP V2 is required, not just recommended,” the company wrote in the same notice. The posture follows from the data: V2 has been Circle’s recommended path since it was announced on November 14, 2025, and the older rails are now being allowed to decay by design.
The 27-Chain Protocol Circle Is Moving Everyone To
CCTP — the Cross-Chain Transfer Protocol — is the messaging layer that lets developers, issuers, and blockchain ecosystems natively move USDC and EURC between networks and permissionlessly wrap third-party assets. Version 2 is not a patch on V1; it runs on separate contracts and APIs and is not backward compatible. Circle’s stated case for forcing the move rests on three capabilities V1 never had: Standard and Fast Transfer modes, programmable hooks that trigger automated actions on the destination chain once USDC lands, and coverage across 27 supported blockchains.
That chain count is the concrete expansion. V2’s 27-network footprint spans the EVM and non-EVM chains that now anchor most USDC volume, where V1’s reach stopped at a smaller set of legacy networks. For an integrator, migration is a contract swap with real work attached — new addresses, new APIs, and a burn-and-mint flow that has to be re-pointed before the old one goes dark.
The two settlement speeds are the practical upgrade. Standard Transfer works like V1’s burn-and-mint flow, finalizing once the destination chain confirms the burn. Fast Transfer cuts the wait by having an operator pre-fund liquidity on the destination, so a sender can receive USDC before the source-chain attestation settles. Programmable hooks build on that: a developer can attach a callback that fires on the destination chain the moment USDC arrives, which is what lets a bridge or lending market automate the second half of a cross-chain deposit.
What Tightens Today, and What Stops on December 1
The October 31 change is a reduction, not a shutdown. Circle’s wording is precise: “CCTP V1 (Legacy) burn limits will be reduced starting October 31, 2026, and performance will gradually decrease over a one month window to support a smooth transition to zero usage.” That “smooth transition to zero usage” is a forecast, not a guarantee — mechanically, each day a little less USDC can be burned and minted through the legacy contracts.
December 1 is the harder line. “CCTP V1 (Legacy) contracts will be paused on December 1, 2026, and any integration still pointing at them will stop transferring USDC crosschain,” Circle states. That is the date an unmigrated application stops being a slow bridge and becomes a dead one. The 31-day gap between the first limit cut and the pause is the buffer Circle is giving integrators to finish the swap.
What does not happen today matters as much as what does. USDC keeps moving; no contract is frozen on October 31, and the December 1 pause applies to V1 specifically, not to V2 or to the stablecoin itself. The risk is concentrated in whatever still depends on the legacy rails, not in USDC’s wider circulation.
The timing is not arbitrary. USDC has become the settlement layer for a large share of cross-chain activity, and Circle is consolidating that traffic onto one protocol rather than maintaining two. Keeping V1 alive alongside V2 would split liquidity, duplicate security review, and leave the legacy contracts as a slower, older attack surface. From Circle’s view, the deprecation is a consolidation play with a deadline attached.
The Noble Exit Runs on a Separate Clock
One corner of the ecosystem is exiting faster than the rest. In a separate notice , Circle said it is discontinuing USDC and CCTP V1 on the Noble blockchain, and stated plainly: “Noble will not receive CCTP V2.” That makes Noble the one chain with no upgrade path, which is why its holders are already inside a tighter schedule. BlockchainReporter covered the Noble halt when it was first announced; the CCTP V1 deprecation starting today is the umbrella event it sits under.
New minting of USDC on Noble through Circle Mint was disabled on October 13, 2026. Redemptions from Noble remain available until January 12, 2027, when the Noble USDC contract and CCTP routes are fully paused, and a manual redemption portal opens the following day. Noble holders have a 91-day exit window in total, but the burn-limit reduction that begins today arrives only 18 days into it — the main cross-chain exit narrows well before the window closes. Circle said it will publish a shortlist of known exit venues and that it is not operating its own exit UI.
What the 351-Day Notice Was Supposed to Buy
Circle announced V2 on November 14, 2025 and begins the V1 wind-down today — a 351-day notice window, close to a full year. Circle leans on that figure to argue the transition is orderly: “We announced this transition on November 14, 2025, giving the ecosystem nearly a year of notice to migrate to CCTP V2.”
The countercase is that a long notice period only helps integrators who acted on it. Any application that stayed on V1 through the deadline now faces a compressed repair window — 31 days — instead of the year it was offered. Circle calls the transition “transparent, predictable and minimally disruptive,” but the disruption is not distributed evenly: it lands on whoever has not yet migrated, and Circle does not publish a count of how many integrations remain on V1.
Circle is also explicit about what CCTP is not. The service is non-custodial — Circle Technology Services does not hold or control user assets — transfers are irreversible, and CCTP “has not been reviewed or approved by NYDFS or any other regulatory authority.” Those caveats matter for anyone treating a bridge as neutral plumbing: the V1-to-V2 swap is a technical migration, not a custodial event, and a wrong destination address still cannot be recovered.
Who Is Affected, and What Circle Is Not Shutting Down
The deprecation splits into three audiences. Developers and issuers still on V1 have 31 days to repoint their integrations, or their transfers fail after December 1. Institutional and self-custody USDC holders on Noble should move off before January 12, 2027, through a CEX that supports Noble deposits, a DEX swap, or a CCTP V1 burn. Circle Mint customers on Noble lost new-minting access on October 13 but retain redemptions until the January deadline. End users who only interact with already-migrated apps see no change.
What Circle is not shutting down is just as material. CCTP V2 keeps expanding across EVM and non-EVM chains. Inside the Cosmos ecosystem where Noble sits, Circle’s presence does not end with Noble’s exit — Injective and other IBC-connected chains remain active partnerships, and USDC continues to serve as a settlement asset across Cosmos DeFi. For readers following Circle’s broader stablecoin business, the revenue trajectory is tracked in our earlier coverage of Circle’s USDC results .
The next observable signal is December 1, when V1 contracts are paused and it becomes visible how many integrations failed to move in time. January 12, 2027 follows with the Noble contract freeze and the start of manual redemptions. Between now and then, the practical check is simple: any wallet or app still showing a CCTP V1 route should be treated as expiring, not permanent.
.jpg)
.jpg)