Relay vs. CCTP
Rift Research
Last updated
TLDR: Relay is a cross-chain intents and payments protocol. CCTP is Circle’s native USDC burn-and-mint protocol. Consider Relay when you need fast small-to-mid transfers and payments across many networks. Consider CCTP when you are moving pure USDC to USDC between supported chains. Confirm the live winner on rates.gg.
What each protocol is
Relay. Relay is a cross-chain intents protocol. Users deposit into a per-chain Depository; solvers fill on the destination; a dedicated settlement chain and oracle reimburse the solver. Official docs: Relay Docs. App: relay.link.
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 | Relay | CCTP |
|---|---|---|
| Role | Cross-chain intents and payments protocol | Circle native USDC burn-and-mint |
| Fee | Solver spread plus small protocol components, quoted per order | Check the applicable CCTP version and route: transfer fees and network gas depend on transfer mode and chain |
| Coverage | Networks and assets supported by the selected Relay route | Circle-supported USDC domains (Ethereum, L2s, Solana, Aptos and others) |
| Settlement | Solver fronts destination liquidity; protocol settles after proof | Native USDC (burn source, mint destination) |
| Trust model | Non-upgradable Depository contracts; Allocator-authorised withdrawals; audited settlement stack | Circle attestation / issuer |
| Good fit for | Fast small-to-mid transfers and payments across many networks | Native USDC transfers between supported domains |
| Docs | Relay Docs | Circle CCTP Docs |
Where each fits
Relay may fit when:
- Speed on a small or mid-size transfer matters most
- You need a long list of networks from one integration
- The job is a payment or simple transfer, not a multi-step DeFi action
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. Relay 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 Relay when you need fast small-to-mid transfers and payments across many networks.
- 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, Relay or CCTP?
Neither has a universal price advantage. Relay: Solver spread plus small protocol components, quoted per order. 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 Relay 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 Relay and CCTP docs?
Relay: Relay Docs. CCTP: Circle CCTP Docs. Live rate comparison: rates.gg.
Official sources
- Relay docs: Relay Docs
- Relay app: relay.link
- Relay — How Relay works: docs.relay.link/how-relay-works
- Relay — Protocol design: docs.relay.link/references/protocol/how-it-works
- Relay — Security and audits: docs.relay.link/references/protocol/security
- 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 Relay 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.