Cross-Chain Transfer Protocol
Cross-Chain Transfer Protocol
Native crosschain transfers
CCTP enables USDC to flow natively 1:1 between blockchains, unifying liquidity and simplifying user experience.

Trusted By The Community


Why use cross-chain transfer protocol?
The most secure way to transfer USDC crosschain

Deliver the best crosschain experiences


CCTP: More powerful, more flexible
CCTP | CCTP V1 (Legacy)* | |
|---|---|---|
Features | ||
Standard Transfer | ||
Fast Transfer | ||
Hooks | ||
User experience | Advanced functionalities | Standard functionalities |
Backwards | N/A | |
Blockchains | Arbitrum, Avalanche, Base, Codex, Ethereum, HyperEVM, Ink, Linea, OP Mainnet, Plume, Polygon PoS, Sei, Solana, Sonic, Unichain, World Chain, and XDC | Aptos, Arbitrum, Avalanche, Base, Ethereum, Noble, OP Mainnet, Polygon PoS, Solana, Sui, and Unichain |
how it works
Programmatic burning & minting
Initiate transfer on source chain
A user accesses your app to transfer USDC and specifies the recipient wallet address on the destination chain. Your app facilitates a burn of USDC on the source chain.
Fetch signed attestation from Circle
Circle observes and attests to the burn event on the source chain. With Fast Transfer, the attestation is available immediately. Your app requests the attestation from Circle.
Complete transfer on destination chain
Your app uses the attestation to mint USDC for the recipient on the destination chain. With Hooks, additional operations trigger automatically.
Flexible pricing to meet your needs

Standard Message Transfer
Standard USDC Transfer
Fast Message Transfer
Fast USDC Transfer
Hooks

*Phase-out commencing on 7/31/26
**CCTP fees are subject to change. Circle will provide advanced notice.
Resources
FAQs
CCTP is a permissionless onchain utility that enables the flow of USDC across chains through native burning and minting. With CCTP, USDC is effectively teleported from one blockchain to another.
CCTP V2 is now the canonical CCTP. As such, Circle is aligning the ecosystem on a single, more powerful standard that can scale to meet the needs of developers and the applications they’re building.
CCTP V1, now CCTP V1 (Legacy), has served developers well since its launch in 2023, but by contrast it is limited to Standard Transfer functionality only. CCTP V1 (Legacy) will stay active on its current 11 supported blockchains, but there will be no new chain integrations or feature updates. Its phase-out will begin on July 31, 2026, leading to full contract pause at the end of the deprecation period.
Start your migration today with our step-by-step CCTP Migration Guide or visit our docs to begin integrating CCTP for the first time.
CCTP serves as permissionless infrastructure for developers to build on top of, or integrate into, their existing apps, bridges, exchanges, and wallets.
CCTP is intended for developers looking to integrate advanced crosschain functionalities for faster speeds and enhanced composability.
Lock-and-mint bridges are applications that lock a user's native USDC within a smart contract on a source chain and then mint a wrapped or bridged form of USDC on a destination chain. This process incurs additional trust assumptions and can result in poor UX due to the fragmentation of liquidity.
In contrast, CCTP enables USDC to move securely 1:1 between blockchains via a native burn-and-mint process. The result is greater capital efficiency and unified liquidity with no creation of bridged forms of USDC.
As a low-level primitive, CCTP can be embedded within existing bridge apps to replace their lock-and-mint functionality.
Liquidity pool bridges are applications that hold large pools of USDC on a source chain and a destination chain in order to facilitate crosschain swaps for end users. This process incurs additional trust assumptions and fees associated with the liquidity tied up on each chain.
In contrast, CCTP enables USDC to move securely 1:1 between blockchains via a native burn-and-mint process. The result is greater capital efficiency and unified liquidity without the need for large pools of USDC tokens.
As a low-level primitive, CCTP can be embedded within existing bridge apps to replace their liquidity pool functionality. Alternatively, CCTP could be used by the bridge provider to programmatically rebalance their liquidity pools behind the scenes and reduce operational costs.
No, CCTP is permissionless, which means any developer can integrate via our docs and GitHub repo.
For CCTP transfers, there would be a gas fee on the source blockchain and a gas fee on the destination blockchain. The app that integrates with either version would be responsible for determining how gas fees are handled and/or passed on to the end user.
An additional fee may be collected when the stablecoin is minted on the destination chain, based on the amount minted. Refer to the associated fees for more information.
No, the canonical CCTP operates with a distinct set of V2 smart contracts and APIs, and has formed its own distinct network of supported blockchains as it is not backwards compatible with CCTP V1 (Legacy) smart contracts.
Note: CCTP V1 (Legacy)’s phase-out commences on 7/31/26.
