What is CCTP?
CCTP, short for Cross-Chain Transfer Protocol, is Circle's permissionless protocol for moving native USDC between blockchain networks. It burns USDC on the source chain and mints an equivalent amount on the destination chain. The result is always native USDC, not a wrapped or synthetic version. Circle launched CCTP in 2023 and released CCTP V2 in March 2025.
The protocol is permissionless. Any developer can integrate it directly through Circle's documentation and GitHub repository without needing an account or approval from Circle.
How does CCTP work?
A CCTP transfer happens in three steps.
- User calls Circle's TokenMessenger contract on the source chain. This burns the USDC and emits a message containing the recipient address and the destination chain identifier.
- Circle's off-chain Iris attestation service observes the burn event and signs a message confirming it happened. This signed attestation is the proof that allows the next step to proceed.
- Anyone holding the signed attestation can call the MessageTransmitter contract on the destination chain. The contract verifies the signature and mints native USDC for the recipient.
No funds are locked anywhere in this process. The burn on the source chain and the mint on the destination chain are mathematically linked through the attestation. Nothing sits in a bridge vault waiting to be stolen.
CCTP V1 vs. CCTP V2
CCTP V2, launched on Ethereum and Avalanche in March 2025 and expanded to 13 or more chains by late 2025, introduced two significant changes.
- Fast Transfer settles in roughly 8 to 20 seconds across supported chains by making Circle's attestation available immediately rather than waiting for blockchain finality on the source chain. Standard Transfer waits for full source-chain finality before the attestation is issued, which takes longer depending on the network. Fast Transfer carries a small on-chain fee per transaction. Standard Transfer has no on-chain fee from Circle.
- Hooks allow developers to attach additional on-chain actions that trigger automatically when USDC is minted on the destination chain. A transfer could deposit USDC into a DeFi protocol, execute a swap, or trigger a smart contract function in the same transaction as the mint, rather than requiring a separate follow-up call.
What chains does CCTP support?
As of 2026, CCTP V2 operates across 13 or more mainnet chains, including Ethereum, Arbitrum, Base, Optimism, Avalanche, Polygon, Solana, Sui, and Noble. Solana support was added in October 2025. Additional chains including Aptos and Unichain are planned.
How is CCTP different from a traditional bridge?
The distinction matters for anyone thinking about cross-chain USDC movement.
Traditional cross-chain bridges use a lock-and-mint model. They lock USDC in a smart contract on the source chain and issue a wrapped token on the destination chain. That wrapped token is a derivative backed by the locked collateral. The locked funds create a honeypot. The exploits that have led to some of the largest losses in crypto history, including the Ronin Bridge hack and the Wormhole exploit, targeted exactly this structure.
CCTP holds nothing. There is no locked vault. There is no wrapped token. The burn destroys the source-chain USDC and the mint creates new destination-chain USDC. Circle's attestation links the two events. The risk profile is fundamentally different.
Why CCTP matters for stablecoin payments
CCTP changes the risk calculus for moving USDC across chains as part of a payment flow. For stablecoin orchestration platforms routing cross-border payments, the choice between a traditional bridge and CCTP is a direct risk management decision.
Using CCTP removes the smart contract custody risk that has historically been the biggest single vulnerability in cross-chain infrastructure. It also eliminates wrapped token fragmentation. A USDC received via CCTP is native on the destination chain. It can be used anywhere USDC is accepted on that chain without any unwrapping step.
The limitation is that CCTP only works for USDC. For other stablecoins or assets, a different cross-chain mechanism is still required. Platforms moving USDT or other tokens across chains do not have an equivalent issuer-backed protocol available, and traditional bridge risks still apply for those transfers.
