Circle's Cross-Chain Transfer Protocol (CCTP)

CCTP is Circle's native USDC bridging infrastructure - the only production bridge that moves actual USDC (not an IOU or wrapped version) between chains. USDC is burned on source and minted on destination through Circle's attestation model. No liquidity pools to drain. No wrapped asset to depeg. Just Circle's regulated infrastructure verifying and issuing USDC directly on each chain. It's the most boring and therefore most elegant cross-chain mechanism for USDC transfers.

How CCTP Works: Burn -> Attest -> Mint

The complete lifecycle of a CCTP transfer. Watch the animation to see how USDC flows without any intermediate wrapped asset.

Step 1 / 6
1. User calls burn on source: The user calls Circle's BurnMathematics.burn() on the source chain, sending USDC to the burn contract. Circle's USDC supply on the source chain decreases by the burned amount.

CCTP vs Wormhole Token Bridge vs Stargate

Three ways to move USDC cross-chain - fundamentally different risk/utility tradeoffs. Toggle rows to compare.

Feature
CCTP
Wormhole Token Bridge
Stargate
Mechanism
Burn-and-mint (native USDC)
Lock-and-mint (wrapped USDC)
Liquidity pool (lpUSDC)
Asset on dest
Circle-minted native USDC
Wormhole wUSDC (bridge IOU)
Stargate lpUSDC (pool token)
Peg risk
None
Low (audited reserves)
Low (pool depth)
Liquidity pool risk
None
Moderate (large TVL)
High (LP can be drained)
Speed
~2-4 min
~5-10 min
~30s (instant finality)
Supported assets
USDC only
Many (any token)
Many (any token)
General message passing
No
Yes
Yes (via LayerZero)
Best for
Large stablecoin transfers, yield arb
Multi-token bridging, Solana routes
Fast, small transfers (hop, across)

Cross-Chain USDC Arbitrage Calculator

CCTP's primary use case is moving USDC between chains to capture yield differentials. Calculate whether the spread justifies the bridging cost.

Yield Differential
+3.0%
Gross Yield Earned
$575
Bridge Cost (CCTP)
$45
Net Profit
$530
OK Worth bridging - 14-day arb generates $530 net after fees

The Attestation Model in Detail

CCTP uses Circle's verifier network rather than a typical guardian or validator multisig. Here's how the cryptographic verification works.

?
Burn Event Observed
Circle's verifier nodes continuously monitor all CCTP-supported chains. When a user burns USDC, the contract emits a BurnToken event with the amount, destination domain, and recipient.
?
Attestation Created
Circle's verifier nodes independently verify the burn event against the source chain's state. A threshold of signers produce a signed attestation message containing the burn proof. This is Circle's key security mechanism.
?
Attestation Submitted to Dest
The attested burn proof is submitted to the destination chain's CCTP MessageReceiver contract by any relayer (often the destination protocol's infrastructure).
?
MintRouter Mints USDC
The MessageReceiver verifies Circle's signature using on-chain stored verifier public keys. Once verified, it calls MintCA to mint the exact amount of USDC to the recipient address.

Related Reading

Go deeper on USDC, cross-chain infrastructure, and stablecoin risk.

Cross-Chain Overview
LayerZero, Wormhole, Axelar - how they compare to CCTP for cross-chain USDC transfers.
LayerZero Deep Dive
LayerZero V2 DVNs, OFT standard, and how LayerZero integrates CCTP for USDC transfers.
Wormhole Deep Dive
How Wormhole's guardian network compares to Circle's attestation model for USDC bridging.
USDC Deep Dive
Full breakdown of USDC's reserve model, Circle's minting logic, and how CCTP fits into the USDC ecosystem.
Bridges Overview
Lock-and-mint vs liquidity pool vs burn-and-mint - the three bridge architectures and their risk profiles.
Hyperlane Deep Dive
Sovereign security model - how Hyperlane compares to Circle's centralized attestation approach.