What is CCTP (Cross-Chain Transfer Protocol)?
How it works
A transfer starts when a user — or an app acting on their behalf — calls CCTP's TokenMessenger contract on the source chain. The contract burns the specified amount of USDC and passes a message through the MessageTransmitter contract that records the amount, the destination chain's domain ID, and the recipient address.
Circle runs an off-chain attestation service that watches every supported chain. Once the burn transaction reaches finality, the service signs an attestation — a cryptographic proof that the burn happened. Fetching and relaying that attestation is permissionless: anyone can submit it to the destination chain.
On the destination chain, the MessageTransmitter verifies the attestation signature and instructs the local TokenMessenger to mint the exact burned amount of native USDC to the recipient. Because every mint is matched one-to-one by a burn, no wrapped or synthetic token ever exists — supply is simply conserved across chains.
Standard transfers are bounded by source-chain finality, which means minutes on Ethereum. CCTP V2, released in 2025, added Fast Transfer — Circle fronts the mint from a pre-funded allowance before finality settles, for a fee — and Hooks, which let the mint atomically trigger a follow-up action such as a swap or a deposit into a lending market. Most users never interact with CCTP directly; bridges and routing aggregators integrate it as the underlying USDC rail.
Why it matters
Bridge failures were among DeFi's costliest events: the Ronin ($625M) and Wormhole (~$326M) exploits of 2022 both hit lock-and-mint designs, where attackers minted wrapped tokens without backing. Wrapped assets also fragment liquidity — "USDC.e" trading beside native USDC — and can depeg if the bridge holding the collateral fails. CCTP eliminates that entire risk class for USDC: nothing is locked, so there is no honeypot, and the token that arrives is always native and redeemable. The trade-off is trust in Circle itself — a centralized attester that can pause transfers — which is why CCTP is best understood as extending USDC's existing issuer trust model across chains rather than adding a new one.
Real-world examples
When the Multichain bridge halted in July 2023, wrapped USDC on Fantom fell well below $1 because the collateral backing it was stranded in Multichain's Ethereum contracts. Native USDC moved via CCTP carries no such IOU: Circle launched the protocol on Ethereum and Avalanche in April 2023, and interoperability layers like Wormhole and aggregators like LI.FI adopted it as their USDC rail — a transfer from Ethereum to Base burns tokens on one side and mints Circle-issued USDC on the other.
FAQ
Is CCTP a bridge?
Not in the traditional sense. Bridges typically lock tokens on one chain and issue wrapped copies on another, or swap through liquidity pools. CCTP is a burn-and-mint messaging rail for native USDC — no pools, no wrapped tokens. In practice, bridges and routing aggregators integrate CCTP under the hood, so you may be using it without knowing.
What are the risks of using CCTP?
The main one is centralization: Circle's attestation service is the sole signer, so Circle can pause or censor transfers, and USDC itself supports address freezing. There is also ordinary smart-contract risk, and CCTP only works for Circle-issued assets (USDC, and later EURC) on chains Circle chooses to support.
How long does a CCTP transfer take?
A standard transfer waits for the burn to reach finality on the source chain — minutes on Ethereum, faster on chains with quicker finality. CCTP V2 (2025) introduced Fast Transfer, where Circle advances the mint from a pre-funded allowance before finality, settling in seconds for an extra fee.
Related terms
Go deeper
Browse the complete crypto glossary to explore related terms and concepts.
Browse Glossary