Migrate to CCTP V2 Ahead of CCTP V1 (Legacy) Deprecation

Circle plans to deprecate CCTP V1 (Legacy) between October 31 and December 1, 2026, requiring applications that use its contracts for crosschain USDC transfers to migrate to CCTP V2, now called CCTP. Beginning October 31, V1 burn limits and performance will be progressively reduced, and its contracts will be paused on December 1, ending crosschain transfer functionality for integrations that have not migrated. CCTP V2 uses separate, non-backward-compatible contracts and APIs, supports 27 blockchains, and adds Standard and Fast Transfer modes as well as programmable hooks for automated actions after funds arrive on a destination chain. Developers needing to use the V1 replaceDepositForBurn function to modify a mint recipient or destination caller must do so before January 12, 2026, when that function will no longer be supported. Circle directs developers to its migration guide and support channels, while noting that CCTP is a non-custodial messaging service, transfers are irreversible, and use entails technical, market, and third-party asset risks.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.