Cross-Chain Transfer Protocol (CCTP) is Circle's official mechanism for moving native USDC between blockchains by burning the token on one chain and minting it on another. Instead of locking USDC inside a third-party bridge contract and issuing a wrapped IOU, CCTP routes the value through Circle itself. The result is a cross-chain transfer where both sides of the move are real, Circle-redeemable USDC, with no bridge custody risk in the middle.
​

CCTP is a protocol Circle launched in 2023 that lets applications burn USDC on a source chain and mint an equivalent amount of USDC on a destination chain. Circle operates an attestation service that signs the burn event, and the destination contract verifies that signature before minting. The user ends up with native USDC on the new chain rather than a wrapped representation issued by a bridge.
​

A CCTP transfer has three steps. First, the user calls a deposit function on the source-chain TokenMessenger contract, which burns their USDC and emits a message containing the recipient address and destination domain. Second, Circle's off-chain attestation service observes the burn, waits for the source chain to reach finality, and signs a message authorizing the mint. Third, anyone can submit that signed attestation to the destination-chain MessageTransmitter contract, which verifies the signature and mints the same amount of USDC to the recipient.
​

The user holds nothing in between. Burned USDC ceases to exist on the source chain, and minted USDC comes into existence on the destination chain only after Circle's attestation. The supply of USDC across all chains stays constant.
​

Most cross-chain bridges use a lock-and-mint design. The bridge contract locks the original asset in a vault on the source chain and mints a wrapped version on the destination. Users redeem the wrapped token by sending it back, which burns the wrapper and unlocks the original. The wrapped token's value depends entirely on the bridge contract holding the locked collateral safely.
​

CCTP uses burn-and-mint instead. There is no vault, no wrapped token, and no bridge balance to attack. Burning destroys the source-chain USDC outright, and Circle mints fresh native USDC on the destination chain after attestation. The destination token is the same USDC users get from Circle directly through Mint or through Coinbase, with the same reserve backing and the same redemption path.
​

The big USDC-related bridge losses of the last few years came from lock-and-mint designs where attackers either drained the locked collateral or forged mint authorizations. Wormhole's February 2022 incident and Nomad's August 2022 incident both involved bridge contracts holding wrapped-asset collateral that turned out to be reachable.
​

CCTP narrows the trust surface to Circle. There is no pool of locked USDC for an attacker to drain because the source-chain USDC was burned, not locked. The only way to mint fraudulent USDC on a destination chain through CCTP is to forge a Circle attestation, which requires compromising Circle's attestation infrastructure. That is still a risk, but it is the same trust assumption USDC holders already take on every chain — Circle controls issuance and reserves regardless.
​

The practical consequence is that users who care about counterparty risk on the bridge layer can route USDC through CCTP and stop worrying about a separate set of bridge-contract keys or multisigs.
​

CCTP v1 shipped in 2023 with the basic burn-and-mint flow. Transfers waited for source-chain finality before Circle signed an attestation, which meant Ethereum-originated transfers took roughly 13–19 minutes to clear, and other chains took as long as their finality windows required.
​

CCTP v2 added two changes. The first is Fast Transfer, an opt-in mode that uses Circle's own short-term liquidity to mint on the destination chain before source-chain finality, then settles the underlying burn afterwards. Fast Transfer cuts wall-clock transfer time on slower-finality chains down to seconds, in exchange for a small Fast fee that Circle takes on top of gas. Standard Transfer remains free of any Circle fee. The second change is Hooks, which let an application attach an onchain action to the destination-side mint — for example, swap the USDC into another token immediately on arrival, or deposit it into a lending market — bundling cross-chain movement with whatever the user actually wanted to do with the funds.
​

CCTP support has expanded steadily since launch. The canonical list lives in Circle's developer documentation at developers.circle.com/stablecoins/cctp-supported-blockchains, and it is the only source any integrator should rely on. Names appearing on the list as of 2026 include Ethereum, Avalanche, OP Mainnet, Arbitrum, Base, Polygon PoS, Solana, Linea, Unichain, Sonic, World Chain, and several other chains; Aptos, Noble, and Sui run on the V1 legacy contracts that Circle has scheduled for phase-out. Circle ships new chains at a steady cadence, so the live page is the source of truth before you build a route or quote a user.
​

Two notes. First, not every CCTP-supported chain is on v2 yet — some chains run only the v1 contracts, which means no Fast Transfer and no Hooks on those routes. Second, the destination chain must run a mint-side contract that the source is configured to message; check the route, not just the per-chain support flag.
​

For Standard Transfer, the user pays gas on the source chain to call the burn, and gas on the destination chain to submit the attestation and trigger the mint. There is no Circle fee. End-to-end gas on cheap-L2 routes such as Base-to-Arbitrum sits in the low cents range; routes that touch Ethereum mainnet pay Ethereum-mainnet gas on whichever side touches it.
​

For Fast Transfer in CCTP v2, Circle adds a Fast fee on top of gas. The fee scales with the size of the transfer and is published in Circle's developer docs; the floor is small for retail-size moves. Fast Transfer is opt-in, so users who do not want to pay the fee can simply choose Standard Transfer and wait for finality.
​

CCTP gets called a bridge in casual usage, but it does not work like a bridge in the technical sense. A bridge holds collateral on one chain and issues a derivative on another. CCTP holds nothing — burns delete the source-chain USDC, mints create new destination-chain USDC, and Circle's attestation links the two events. There is no wrapped token, no locked vault, and no bridge balance.
​

For most users, what matters is the user-visible behavior: USDC goes in on one chain and the same amount of USDC comes out on another, settling in seconds with Fast Transfer or in minutes with Standard. From that angle CCTP fills the role a bridge would otherwise play. From a risk angle, the design is closer to native issuance than to bridging.
​

Several general-purpose messaging protocols also move USDC across chains. The trade-offs are worth a side-by-side look.

The header decision is whether the user wants native USDC on the destination chain. CCTP is the most direct way to get it. LayerZero and Wormhole both route USDC through CCTP under the hood for many of their newer USDC products, which means the underlying value movement looks the same as a direct CCTP call. Across uses its own relayer-fronted liquidity model and settles independently. For applications that already integrate one of these messaging stacks, sticking with that stack is often simpler than bolting on a separate CCTP integration.
​

CCTP is a developer protocol, not a consumer product, so users meet it through the apps that integrate it. Common integrations include Coinbase Wallet, Phantom for its Solana-EVM USDC routes, MetaMask Bridges, Bridge.xyz, Ondo for stablecoin movement around its yield products, and the Eco app for routed USDC payments. Many of the major consumer-facing bridges and aggregators (Jumper, Bungee, Squid, Stargate, Mayan, deBridge among others) route USDC through CCTP when both endpoints are CCTP-supported.
​

Verify in the destination wallet that you received native USDC and not a bridged variant before treating it as Circle-redeemable. The contract address on each chain is published on Circle's USDC contracts page; matching it confirms native USDC.
​

For payments and intents, CCTP is the lowest-trust way to land native USDC on a destination chain — which is what most onchain checkouts and payouts ultimately need. Routing layers such as Eco compose CCTP with chain-specific liquidity and intent execution so a payer on one chain can settle a payee on another in native USDC, without requiring either side to manage bridge UX. The protocol-level burn-and-mint stays the same; the orchestration layer handles route selection, fee quoting, and final-leg execution.
​

Mechanism, v1 vs v2 differences, attestation flow, and supported-chain list verified against Circle's developer documentation at developers.circle.com/stablecoins/cctp and the supported-blockchains page. Fast Transfer fees and Hooks behavior reference Circle's CCTP v2 announcement and v2 developer docs. Comparison points for LayerZero, Wormhole, and Across reflect each protocol's published documentation as of 2026; integrations evolve, so verify route specifics in each protocol's docs before building. USDC supply context cross-checked against DeFiLlama's stablecoin dashboard.
​