TL;DR: Circle’s published schedule begins reducing legacy CCTP burn limits from October 31. Noble has a separate January 2027 pause, so holders and integrators need to distinguish the deadlines.
The wind-down of Circle’s legacy cross-chain infrastructure has entered a new scheduled phase, with burn-limit reductions due to begin on October 31. For USDC holders on Noble, that sits inside a longer transition that ends with a planned contract and route pause in January.
The dates matter because a token can remain transferable on its existing chain while one of the routes used to move it elsewhere becomes more restricted.
The general legacy deadline and Noble deadline differ
Circle’s CCTP V1 deprecation notice says burn limits begin reducing on October 31, ahead of a general legacy-contract pause on December 1. It states that V2 uses separate contracts and APIs and is not backward compatible with V1.
Its Noble-specific notice sets January 12, 2027 as the pause date for Noble’s USDC contract and remaining CCTP routes. Noble will not receive V2 support. New Noble minting was scheduled to stop on October 13.
These are the issuer’s published schedules. They should not be replaced with an assumption that every route reached a zero limit immediately on October 31. Circle also warns that, after December 1, Noble exits may be limited to destinations still supporting V1. January 12 therefore does not guarantee every route remains open until that date.
A bridge migration is not just a new interface
When a protocol version uses different contracts and APIs, an application has to change the systems it calls and the assumptions it makes about responses. Updating a logo or displaying a new route name is not sufficient.
Integrators also need to account for transfers already in progress. A source-chain action, an attestation and a destination-chain completion are related steps, and the status of one does not establish that the whole process has finished.
The operational objective is to avoid a gap in which users can begin a transfer that the application no longer knows how to complete. Clear route availability and handling of pending transfers are therefore part of the migration work.
Token identity and chain support both matter
USDC issued on one blockchain is not interchangeable at the interface level with every asset bearing the same ticker elsewhere. A receiving service has to support the actual network and token form being sent.
That distinction becomes more important during a sunset. A venue might support a destination chain while no longer accepting deposits from an older route, or it might require a conversion step with its own terms and liquidity.
The Cosmos community-pool migration proposal illustrates the issue at treasury level, describing a planned move from Noble-issued to Injective-issued USDC. A proposal records an intended process; its publication alone does not prove the migration has completed.
The pause date should not become the first planning date
Circle says remaining Noble balances will be snapshotted on the January pause date, with a manual redemption process beginning the following day and subject to eligibility and compliance requirements. That is a fallback process, not the same experience as an ordinary automated transfer.
For holders and services, the useful preparation is to establish which supported route applies, what conditions govern it and how completion will be verified. An asset arriving at an unintended address or through an unsupported network can create problems that a ticker symbol does not reveal.
The broader lesson is that blockchain availability and issuer support have separate lifecycles. A network can continue operating while a particular stablecoin issuer retires contracts or infrastructure on it.
The current development is the start of the scheduled reduction phase. The next checks should focus on current route status and verified completion, while keeping the December legacy deadline and Noble’s January deadline clearly distinct.
Written by the News Desk and edited by Samuel Rae.
