The answer to “CCTP V1 phase-out: what it changes for USDC bridging” is straightforward: Circle began retiring CCTP V1 on 31 July 2026, making CCTP V2 the path for new integrations. Traders now need to check the route’s contract version, supported chain, settlement fee and USDC representation before sending funds.
CCTP V1 phase-out: what it changes for USDC bridging
Circle’s announcement says the CCTP V1 phase-out began on 31 July 2026. The migration concerns Circle’s Cross-Chain Transfer Protocol, the infrastructure used by applications, exchanges, wallets and bridges to move USDC between chains.
Circle describes CCTP as a native burn-and-mint system: USDC is burned on the source chain and minted on the destination chain after Circle attests to the burn. That differs from a lock-and-mint bridge, which locks USDC and issues a separate wrapped representation. The distinction matters because bridge design changes the liquidity, trust and contract risks a trader is taking. Ethereum’s bridge overview explains the broader difference between cross-chain asset-transfer models.
“CCTP V1, now CCTP V1 (Legacy), has served developers well since its launch in 2023.” — Circle, in its CCTP announcement.
What the change actually touches
The direct target is CCTP V1’s smart contracts and APIs. CCTP V1 remains active on its existing 11 supported blockchains during the deprecation period, but Circle says it will receive no new chain integrations or feature updates before a full contract pause.
CCTP V2 is not backward-compatible with V1. It has a different contract and API set, a different supported-chain network, and additional features including Hooks. Circle’s published comparison lists V2 support for chains including Arbitrum, Avalanche, Base, Ethereum, OP Mainnet, Polygon PoS, Solana, Stellar and others. The exact route still depends on the source and destination pair.
The cost change is therefore operational before it is simply a fee change. A V1 route may stop being available, while a V2 route may require a migration by the bridge or wallet provider. Circle lists no on-chain fee for Standard Transfer and an on-chain fee for Fast Transfer, while also warning that CCTP fees can change. Gas on both source and destination chains remains part of the transaction cost.
What traders should check before sending USDC
- Confirm whether the interface is using CCTP V1, CCTP V2 or another bridge mechanism.
- Check that the exact source-and-destination chain pair is supported by the selected version.
- Verify whether the received token is native USDC or a bridged USDC representation.
- Compare source gas, destination gas, bridge fees, slippage and quoted execution time.
- Send a small test amount when the route, contract version or token representation is unfamiliar.
Where Anyswap fits
Anyswap is one working route to inspect when the required asset and chain pair is available there, but it should not be treated as a substitute for checking the underlying mechanism. The CCTP V1 retirement directly affects a route only when that route or its liquidity operations depend on CCTP V1. Otherwise, the relevant comparison is execution: final token received, total fees, liquidity, confirmation time and the bridge’s trust assumptions.
The practical takeaway is to stop treating “USDC bridge” as a complete route description. After 31 July 2026, the protocol version is part of the trade. A quote that looks cheap can still be wrong for the intended destination if it uses a legacy contract, an unsupported pair or a different USDC representation.
Circle’s 31 July 2026 CCTP announcement is the controlling source for the phase-out date, supported-chain split, fee model and migration status.