Community Trust ScoreVerified
Circle has initiated the scheduled reduction of burn limits for its legacy Cross-Chain Transfer Protocol (CCTP) infrastructure, with the process beginning on October 31. This development marks the start of a phased wind-down for CCTP V1, which Circle states is not backward compatible with the newer V2 system. For users and integrators holding USDC on the Noble chain, this reduction phase precedes a specific pause date of January 12, 2027, for Noble’s USDC contract and remaining CCTP routes.
Distinction Between General and Noble Deadlines
Circle’s deprecation notice for CCTP V1 outlines a timeline where burn limits begin decreasing on October 31, leading up to a general legacy-contract pause on December 1. The company emphasizes that CCTP V2 utilizes separate contracts and APIs, meaning it does not support backward compatibility with V1. Integrators moving from V1 to V2 must modify the systems they call and adjust their assumptions regarding response data. Simply updating a logo or displaying a new route name is insufficient for a functional migration.
Noble has a distinct schedule separate from the general legacy pause. According to Circle’s Noble-specific notice, new minting on Noble was scheduled to stop on October 13. The pause date for Noble’s USDC contract and its remaining CCTP routes is set for January 12, 2027. Noble will not receive support for CCTP V2. Circle warns that after the December 1 general pause, exits from Noble may be limited to destinations that still support V1. Consequently, the January 12 date does not guarantee that every route will remain open until that specific day.
Operational Requirements for Migration
The transition from CCTP V1 to V2 requires more than interface updates. Because the protocol versions use different contracts, applications must account for transfers already in progress. A transfer involves a source-chain action, an attestation, and a destination-chain completion. The status of one step does not confirm that the entire process is finished. The operational goal is to prevent gaps where users initiate a transfer that the application can no longer complete. Clear route availability and the handling of pending transfers are essential components of this migration work.
Token identity and chain support are critical factors during this sunset period. USDC issued on one blockchain is not interchangeable at the interface level with assets bearing the same ticker on other networks. A receiving service must support the specific network and token form being sent. A venue may support a destination chain while no longer accepting deposits from an older route, or it may require a conversion step with specific terms and liquidity conditions. The Cosmos community-pool migration proposal illustrates this at the treasury level, describing a planned move from Noble-issued to Injective-issued USDC. However, the publication of a proposal does not prove that the migration has been completed.
Circle states that remaining Noble balances will be snapshotted on the January 12, 2027, pause date. A manual redemption process will begin the following day, January 13, 2027. This process is subject to eligibility and compliance requirements and serves as a fallback rather than an ordinary automated transfer. For holders and services, preparation involves establishing which supported route applies, understanding the governing conditions, and verifying completion. A network can continue operating while a stablecoin issuer retires specific contracts or infrastructure on it, meaning blockchain availability and issuer support have separate lifecycles.
Frequently Asked Questions
When does the Noble USDC contract pause occur?
The pause date for Noble’s USDC contract and remaining CCTP routes is January 12, 2027. New Noble minting was scheduled to stop on October 13.
Will Noble receive support for CCTP V2?
No, Noble will not receive V2 support. After the general legacy-contract pause on December 1, Noble exits may be limited to destinations still supporting V1.
