Across vs. CCTP
Rift Research
Last updated
TLDR: Across is an intent-based interoperability protocol. CCTP is Circle’s native USDC burn-and-mint protocol. Consider Across when you are moving canonical USDC or ETH between major chains and care about speed. Consider CCTP when you are moving pure USDC to USDC between supported chains. Confirm the live winner on rates.gg.
What each protocol is
Across. Across is an intents protocol for bridging and cross-chain swaps. Relayers front destination liquidity. Across advertises approximately two-second fills on supported mainnet routes; actual timing depends on the route. Its intent settlement and refund mechanisms are separate from that initial fill. Official docs: Across Docs. App: across.to.
CCTP. CCTP (Cross-Chain Transfer Protocol) provides Circle’s burn-and-mint path for native USDC. This comparison focuses on that USDC flow; Circle also documents separate CCTP support for non-USDC assets. USDC is burned on the source chain and minted on the destination after a Circle attestation. There is no bridge liquidity pool and no wrapped USDC. Official docs: Circle CCTP Docs. App: www.circle.com/cross-chain-transfer-protocol.
Short version
| Dimension | Across | CCTP |
|---|---|---|
| Role | Intent-based interoperability protocol | Circle native USDC burn-and-mint |
| Fee | Market-quoted relayer spread and LP fee; no separate flat protocol toll | Check the applicable CCTP version and route: transfer fees and network gas depend on transfer mode and chain |
| Coverage | Supported mainnet networks, with availability determined by the exact token pair and route | Circle-supported USDC domains (Ethereum, L2s, Solana, Aptos and others) |
| Settlement | Canonical assets delivered by bonded relayers | Native USDC (burn source, mint destination) |
| Trust model | Relayer-funded fills and the settlement and dispute mechanisms of the deployed Across contracts | Circle attestation / issuer |
| Good fit for | Canonical USDC and ETH transfers between supported chains | Native USDC transfers between supported domains |
| Docs | Across Docs | Circle CCTP Docs |
Where each fits
Across may fit when:
- You are moving USDC or ETH between major supported chains
- Fast destination fills matter; confirm the estimate for your route
- You want a dedicated intent rail rather than a meta-aggregator
CCTP may fit when:
- The asset is USDC on both sides
- Both chains are CCTP domains
- You want issuer-native USDC without relying on a traditional bridge liquidity pool; transfer limits and service availability still apply
Key differences
CCTP’s native USDC flow avoids a traditional bridge liquidity pool. Across covers a different trade or transfer workflow. A routed workflow can also use CCTP as an underlying component. CCTP is a useful benchmark for USDC transfers, but it is not automatically the cheapest complete route. Compare transfer mode, gas, quote fees, delivery time and the exact destination asset. Circle’s CCTP documentation describes the available transfer modes and asset scope.
When to use which
- Use Across when you are moving canonical USDC or ETH between major chains and care about speed.
- Use CCTP when you are moving pure USDC to USDC between supported chains.
- If both can quote the same route, take the better net output after fees, time and settlement type. Check that print on rates.gg.
FAQ
Which is cheaper, Across or CCTP?
Neither has a universal price advantage. Across: Market-quoted relayer spread and LP fee; no separate flat protocol toll. CCTP: Check the applicable CCTP version and route: transfer fees and network gas depend on transfer mode and chain. Compare executable quotes for the same size, destination and time window, including gas, underlying venue costs and any extra transfer. Expected output and minimum received are different figures; compare like with like.
Is Across a substitute for CCTP?
Only on overlapping pairs and chains. When both can quote the same route, take the better net output after fees and time. When only one supports the asset or chain, that one is the only option.
Where are the official Across and CCTP docs?
Across: Across Docs. CCTP: Circle CCTP Docs. Live rate comparison: rates.gg.
Official sources
- Across docs: Across Docs
- Across app: across.to
- Across — Introduction: docs.across.to/introduction
- Across — Features and fill times: docs.across.to/introduction/features
- Across — API reference: docs.across.to/api-reference
- CCTP docs: Circle CCTP Docs
- CCTP app: www.circle.com/cross-chain-transfer-protocol
- CCTP — CCTP overview: developers.circle.com/cctp
- CCTP — Supported chains and domains: developers.circle.com/cctp/concepts/supported-chains-and-domains
- CCTP — CCTP API: developers.circle.com/api-reference/cctp
Get the Best of Both With Rift
Rift is a strong alternative to choosing between Across and CCTP. It brings routes from both together with additional venues on supported pairs, comparing available quotes to find the best net execution for your order. You get the strengths of both through one API.
Rift adds no router fee and uses secure hardware enclaves to enforce noncustodial execution. Underlying venue fees, spreads and network costs still apply, and availability depends on the asset, chain and order size. The live quote shows the route and expected output.