How CCTPv2 Changes Crosschain USDC Transfers

TL;DR: CCTP (Cross-Chain Transfer Protocol) is Circle's official protocol for moving native USDC between chains using a burn-and-mint mechanism. No wrapped tokens. CCTPv2 is the upgraded version now in production, introducing Fast Transfer (seconds-level settlement), Hooks (post-transfer composability), and expanded chain support. Across integrates CCTP under the hood, so you get native USDC on the destination chain with sub-minute fills, automatic route optimization, and a single-transaction experience. Best route, automatically.

There's a version of USDC on Arbitrum that is actually USDC — issued by Circle, backed by Circle's reserves, redeemable with Circle. And there's a version that's a wrapped IOU from whatever bridge moved it there. These are not the same thing. One is a dollar. The other is a promise from a smart contract that it's a dollar.

CCTP exists to make sure you always get the real one.

CCTP (Cross-Chain Transfer Protocol) is Circle's permissionless protocol for transferring native USDC between blockchains using a burn-and-mint mechanism. Instead of locking tokens on one chain and issuing a wrapped version on another, CCTP burns USDC on the source chain and mints fresh native USDC on the destination. The supply stays constant. The USDC you receive is identical to USDC minted directly by Circle on that chain.

This matters more than it sounds. Wrapped USDC creates fragmentation. Each bridge's wrapped version is a different token with different liquidity, different DeFi integrations, and different risk profiles. If the bridge that created your wrapped USDC gets exploited, your tokens could depeg even though Circle's actual reserves are fine. Native USDC doesn't have this problem. It's fungible with every other USDC on that chain regardless of how it got there.

CCTP v1 launched in April 2023. Any bridge, protocol, or application can integrate it. It's permissionless infrastructure from the issuer of the world's most widely used regulated stablecoin. Over its lifetime, CCTP has processed more than 5 million transfers totaling over $110 billion in volume.

CCTPv2 launched on March 11, 2025, and is now the canonical version of CCTP, introducing three major capabilities: Fast Transfer, Hooks, and an expanded network of supported blockchains. CCTP v1 is now designated "Legacy" and will begin its phase-out on July 31, 2026.

The core burn-and-mint mechanism is the same, but v2 meaningfully upgrades the speed and composability of the protocol.

Fast Transfer is the headline improvement. In v1, Circle's attestation service waited for hard finality on the source chain before signing off on the burn — roughly 13 to 19 minutes for Ethereum and L2 chains. Fast Transfer changes this by attesting after soft finality, which reduces settlement to seconds rather than minutes. During the window between soft and hard finality, the burned USDC amount is backed by Circle's own Fast Transfer Allowance. The result is near-instant crosschain transfers at the protocol level, without needing a third-party relayer. Fast Transfer carries a small onchain fee per transaction (approximately 1 basis point from Arbitrum, and low single-digit basis points from other chains).

Standard Transfer preserves the original v1 flow for those who want it: attestation after hard finality, with zero protocol fee. This is the option for large, planned transfers where speed doesn't matter and you want to minimize cost.

Hooks enable developers to trigger arbitrary smart contract actions atomically alongside a USDC transfer — depositing into a lending protocol, executing a swap, funding a treasury — all without added trust assumptions. This makes CCTP composable in ways v1 never was, turning a simple transfer into a programmable crosschain action.

CCTPv2 is now live on a growing list of blockchains including Ethereum, Arbitrum, Avalanche, Base, Linea, Optimism, Polygon, Solana, Sonic, Unichain, World Chain, and others — with Circle continuing to expand chain support. Native USDC and CCTP are already live on Aptos as of early 2026, and Circle has announced plans for Sui as well.

CCTP uses a burn-and-mint model where USDC is destroyed on the source chain and recreated on the destination, while intents-based bridges like Across use relayers who front capital to fill orders instantly. These aren't competing approaches. They solve different parts of the same problem.

The burn-and-mint flow:

With Standard Transfer, the bottleneck is step 2. Hard finality takes 13–19 minutes on Ethereum and L2s. With Fast Transfer, Circle attests after soft finality, collapsing that wait to seconds — but it comes with a small fee.

Intents-based bridges work differently. You sign an order. A relayer sees it, fronts their own USDC on the destination chain, and delivers your tokens in seconds. The relayer gets reimbursed later through the settlement process. You don't wait for settlement because someone else absorbed that wait for you, in exchange for a small fee.

With v2's Fast Transfer, the raw speed gap between CCTP and intents-based bridges has narrowed significantly. But intents still offer distinct advantages: multi-token support beyond USDC, automatic route optimization across multiple settlement paths, and a simpler user experience — particularly for users who don't want to think about which transfer mode to use.

Across integrates CCTPv2 as a settlement path, combining intelligent routing with the native USDC guarantee of Circle's burn-and-mint protocol. When CCTP is the optimal route for your transfer, Across uses it automatically. You don't choose. You don't even notice.

Across was the first crosschain bridge to offer auto-finalized CCTPv2 transfers. When the routing algorithm selects CCTPv2, users complete a single transaction — Across's finalizer infrastructure monitors Circle's attestation service and automatically submits the mint transaction on your behalf. No second transaction required.

Here's how the routing works in practice. You bridge USDC through Across. The system evaluates your transfer and selects the optimal path:

Either way, you get sub-minute fills and native USDC. The routing is automatic and optimizes for speed and cost on every transfer.

This is what good infrastructure abstraction looks like. CCTPv2 is excellent settlement and transfer technology. Across is an excellent execution layer. Stacking them gives you automatic route optimization you can't get from CCTP alone, and multi-asset, multi-chain coverage you can't get from a USDC-only protocol. You get the best route automatically every time because Across evaluates CCTPv2 alongside every other available path and picks the one that's optimal for your specific transfer.

For large USDC transfers, this combination is particularly strong. CCTPv2 supports high-value mints — up to $10M in a single transaction through Across — and the native USDC guarantee matters more as the dollar amount goes up. Nobody wants $5M in wrapped USDC if native is available.

What is CCTP? CCTP (Cross-Chain Transfer Protocol) is Circle's official protocol for moving native USDC between blockchains. It uses a burn-and-mint mechanism: USDC is burned on the source chain and minted as native USDC on the destination chain. This eliminates wrapped token risk. CCTP is permissionless and can be integrated by any bridge or application.

How long does a CCTP transfer take? It depends on the transfer mode. CCTPv2's Fast Transfer settles in seconds by attesting after soft finality, with a small onchain fee. Standard Transfer settles after hard finality — roughly 13 to 19 minutes for Ethereum and L2 chains — with no protocol fee. Bridges like Across that integrate CCTPv2 can further streamline the experience with automatic route selection and single-transaction finalization.

Does Across use CCTP? Yes. Across integrates CCTPv2 as a settlement path and uses it automatically when it's the optimal route for a USDC transfer. Across was the first bridge to offer auto-finalized CCTPv2 transfers — users complete one transaction, and Across handles the rest. You don't need to choose between Across and CCTP.

What's the difference between native USDC and wrapped USDC? Native USDC is minted directly by Circle on a given chain and is fully backed by Circle's reserves. Wrapped USDC is a bridge-issued token representing USDC locked on another chain. Native USDC is fungible with all other USDC on that chain. Wrapped USDC carries additional risk: if the bridge that created it is exploited, the wrapped token could depeg.

What's new in CCTPv2 compared to v1? CCTPv2, launched March 2025, introduces three major features: Fast Transfer (seconds-level settlement via soft finality attestation), Hooks (programmable post-transfer actions like swaps or deposits), and expanded blockchain support. Standard Transfer preserves the original v1 flow with no protocol fee. CCTP v1 is now Legacy and will begin phase-out on July 31, 2026.

Across integrates CCTPv2, offering the best of both bridging worlds, with Intents powering smaller transfers, and CCTPv2 powering larger transfers. You get the best route, automatically, every time.

Bridge USDC at app.across.to | Developer docs