Written by Helena Markou
Circle will discontinue support for USDC and its legacy Cross-Chain Transfer Protocol, CCTP V1, on the Noble blockchain. The issuer’s September 10 notice says Noble will not receive CCTP V2, Circle’s next-generation cross-chain protocol. New USDC minting on Noble through Circle Mint is scheduled to stop on October 13, 2026; Circle Mint redemptions remain available through January 12, 2027; and the Noble USDC contract and CCTP routes are scheduled to be fully paused after that. For users, integrators and market operators, the news is a reminder that a stablecoin’s cross-chain usefulness depends on operating continuity, not merely on a token balance visible in a wallet.
Circle has provided a staged process rather than an immediate shutdown. From September 10 through October 12, its Circle Mint customers can continue current Noble access. Between October 13 and January 12, the issuer says new minting will be disabled but redemptions can continue. CCTP V1 burn limits will begin declining on October 31. Circle says that after December 1, exits may be limited to destination chains that still support CCTP V1 burns. The timetable separates different functions—minting, transferring, burning, redeeming and manual processing—that are often collapsed into a single claim that a dollar token is “available” on a network.
That distinction matters for market structure. A token can remain transferable on its native chain while its most reliable issuer-supported exit route narrows. Liquidity may still exist through centralized exchanges or decentralized venues, but the price, execution quality and availability of those routes can change as participants migrate. Circle suggests that institutional and self-custody holders move USDC off Noble using a supporting centralized exchange, a decentralized exchange swap or a CCTP V1 burn route. These are options, not guarantees of equal access or execution. Participants need to assess venue support, transaction costs, operational limits and counterparty exposure before a deadline concentrates activity.
The impact on developers is equally important. Circle tells applications that have integrated CCTP V1 support for Noble to remove Noble as a supported route before January 12, because the relevant routes will stop functioning after the pause. That is a software-release and customer-communication project, not a clerical configuration change. Integrators need to identify deposit addresses, transaction flows, status screens, error handling, support documentation and any contracts or back-office assumptions connected to the route. A cross-chain product can fail in confusing ways if its user interface continues to advertise a path that the issuer no longer supports.
Circle’s post-deadline manual-redemption plan adds another layer. The company says it will take a snapshot of remaining Noble USDC balances on the pause date and open a manual redemption process beginning January 13. Eligibility will require compliance and security checks, a holder-controlled wallet and an address included in the snapshot. This is a sensible fallback mechanism, but it is not operationally equivalent to normal on-chain redemption. Manual processing can involve identity, documentation, timing and eligibility requirements that some users may find burdensome. The practical lesson is simple: contingency processes are not substitutes for timely migration.
The broader issue is protocol-version risk. CCTP V1 and V2 are infrastructure layers, but their deprecation affects the economic life of assets and applications on connected chains. “Interoperability” therefore should be measured through the whole lifecycle: issuance, transfer, liquidity, settlement, redemption, developer support, customer communication and recovery when a route closes. A bridge or protocol may be technically functional while becoming commercially unusable because an issuer, exchange or front end has ended support. Conversely, an issuer-supported migration can reduce uncertainty if dates, options and responsibilities are stated clearly.
Noble’s sunset does not mean USDC is disappearing from the broader Cosmos ecosystem; Circle says other IBC-connected partnerships remain active. It does mean that users should distinguish ecosystem participation from support for a specific chain and protocol version. The important dates are now visible. The quality of the transition will depend on whether holders migrate before route limits tighten, whether integrators remove obsolete paths, and whether market venues provide workable exits. Stablecoin infrastructure earns trust not only when it launches a new connection, but when it winds down an old one without stranding users or leaving operational ambiguity.
