What CCTP V1 Deprecation Changes — August 2026
What CCTP V1 deprecation changes in August 2026 is straightforward: Circle is retiring the legacy USDC transport in stages. The phase-out began on July 31, 2026. CCTP V1 remains limited to existing routes, while CCTP V2 becomes the version developers and bridge services should integrate for new transfers and features.
What happened to CCTP V1 on July 31, 2026?
Circle began phasing out CCTP V1, its older system for moving USDC between blockchains. The company’s official CCTP page says V1 will receive no new chain integrations or feature updates and will eventually be fully paused.
The important distinction is between “phase-out” and “shutdown.” July 31 was the start of the transition, not necessarily the moment every existing V1 route stopped working. Applications using V1 therefore need to check their route and migration plan rather than assume that an old transaction will immediately fail.
What is different between CCTP V1 and V2?
Both versions move native USDC by burning it on the source chain and minting it on the destination chain. That avoids creating a separate wrapped version of USDC for every network.
CCTP V2 adds the features that matter most for current cross-chain applications: faster transfers, programmable hooks, and a newer contract and API structure. In practice, V2 is not simply a small software update. It is a separate deployment with its own supported chains, so an application must deliberately use the V2 contracts.
| Question | CCTP V1 | CCTP V2 |
|---|---|---|
| Future integrations | No new chain integrations | Active development path |
| Transfer model | Native burn and mint | Native burn and mint |
| Programmable execution | Limited | Supports hooks and faster-transfer features |
| Developer decision | Migration target | Preferred integration target |
What does the CCTP V1 change mean for bridge users?
For a user, the immediate change is route selection. A bridge or wallet may still show an older CCTP route, but availability, settlement speed, and support can change as the deprecation proceeds. Users should confirm which version a service uses and avoid treating “USDC transfer” as one uniform process.
When the goal is simply to move funds between supported networks, Across bridge is one place to check. Its intent-based routing can use the available cross-chain liquidity and, where appropriate, CCTP V2 for native USDC movement. That gives users a practical route during the transition without requiring them to manage Circle attestations and destination-chain execution themselves.
What should developers do now?
- Identify every CCTP V1 contract, API call, and supported route in the application.
- Verify that the destination chain is supported by CCTP V2.
- Test V2 transfers, including fees, finality, hooks, error handling, and gas requirements.
- Keep a fallback route for periods when a chain or bridge provider is upgrading.
What remains open?
When will CCTP V1 stop completely?
Circle has stated that full contract pause will happen at the end of the deprecation period, but the precise final date remains the key operational detail for teams still using V1.
Will every existing V1 route migrate automatically?
No. Developers and service providers must confirm their own contracts, integrations, and supported routes.
Does CCTP V2 replace every bridge?
No. CCTP V2 is designed for native USDC transport. Bridges remain useful for other assets, different execution flows, and routes where users want a completed destination transaction rather than a manual minting process.