Learn Circle’s CCTP V1 (Legacy) deprecation timeline and how to migrate to CCTP V2 before deprecation begins on October 31 and completes December 1, 2026.
CCTP V1 (Legacy) deprecation begins October 31, 2026 and completes on December 1, 2026, in favor of CCTP V2 – which has been known as CCTP since our November 2025 announcement. CCTP is infrastructure for multichain digital asset management that enables developers, issuers, and blockchain ecosystems to natively transfer USDC and EURC, and to permissionlessly wrap third-party assets.
Circle plans to begin deprecation of CCTP V1 (Legacy) on October 31, 2026 and will complete on December 1, 2026, in favor of CCTP V2 (now simply known as CCTP). We announced this transition on November 14, 2025, giving the ecosystem nearly a year of notice to migrate to CCTP V2. If your application still routes USDC through CCTP V1 contracts, start your migration now. Migration from CCTP V1 (Legacy) to CCTP V2 is required, not just recommended.
CCTP V2 is infrastructure for multichain digital asset management that enables developers, issuers, and blockchain ecosystems to natively transfer USDC crosschain. New integrations should be built on CCTP V2 from the start.
CCTP V2's functionalities deliver a host of benefits over CCTP V1 (Legacy), including:
- Standard and Fast Transfer modes
- Programmable hooks for triggering automated actions on the destination blockchain after USDC arrives, and
- 27 supported blockchains
The path to migrate
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. After that time, CCTP V1 (Legacy) contracts will be paused on December 1, 2026, and any integration still pointing at them will stop transferring USDC crosschain.
Note: If a developer seeks to use "replaceDepositForBurn" to change the mint recipient or destination caller, they must do so prior to January 12, 2026 when this functionality will no longer be supported on CCTP V1.
To begin your migration, start with the CCTP Migration Guide. CCTP V2 uses separate contracts and APIs and is not backward compatible with CCTP V1 (Legacy).
The transition from CCTP V1 (Legacy) to CCTP V2 is designed to be transparent, predictable and minimally disruptive. We’re committed to supporting a clean CCTP V1 (Legacy) deprecation, so reach out to our team on Discord if you hit something unexpected.
CCTP is a crosschain messaging infrastructure service provided by Circle Technology Services, LLC ("CTS"). CCTP is non-custodial; CTS does not hold, control, or transfer user assets. CCTP is not a financial, payment, or advisory service and has not been reviewed or approved by NYDFS or any other regulatory authority. Transfers are irreversible; CTS cannot recover assets sent to an incorrect address. CTS does not vet, endorse, or back third-party assets; such assets are subject solely to the applicable third-party terms and risks. Issuers are solely responsible for their services and compliance with applicable laws. Any fee estimates are non-binding previews; actual fees may differ. Assets are subject to a number of risks, including, but not limited to, price volatility and smart-contract, relay, and bridge vulnerabilities. Availability is subject to change. Developer terms apply.
