LI.FI vs. CCTP
Rift Research
Last updated
TLDR: LI.FI is a cross-chain routing and aggregation layer. CCTP is Circle’s native USDC burn-and-mint protocol. Consider LI.FI when you need broad coverage with an SDK, widget and agent tools. Consider CCTP when you are moving pure USDC to USDC between supported chains. Confirm the live winner on rates.gg.
What each protocol is
LI.FI. LI.FI is a routing and orchestration layer. One integration reaches bridges, DEXs, solvers and yield protocols for same-chain swaps, cross-chain swaps, and multi-step flows. Official docs: LI.FI Docs. App: li.fi.
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 | LI.FI | CCTP |
|---|---|---|
| Role | Cross-chain routing and aggregation layer | Circle native USDC burn-and-mint |
| Fee | Integrator and service fees configured per integration; see LI.FI docs | Check the applicable CCTP version and route: transfer fees and network gas depend on transfer mode and chain |
| Coverage | Supported networks through bridges, DEXs and solvers; coverage varies by route | Circle-supported USDC domains (Ethereum, L2s, Solana, Aptos and others) |
| Settlement | Depends on the winning underlying route (can be wrapped or native) | Native USDC (burn source, mint destination) |
| Trust model | LI.FI router plus each underlying bridge, DEX or solver | Circle attestation / issuer |
| Good fit for | Broad coverage with an SDK, widget and agent tools | Native USDC transfers between supported domains |
| Docs | LI.FI Docs | Circle CCTP Docs |
Where each fits
LI.FI may fit when:
- You need one integration that covers the long tail of chains and tokens
- You want widgets, SDK, MCP and agent tooling in the same stack
- The product is a general-purpose cross-chain app, not a single corridor
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. LI.FI 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 LI.FI when you need broad coverage with an SDK, widget and agent tools.
- 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, LI.FI or CCTP?
Neither has a universal price advantage. LI.FI: Integrator and service fees configured per integration; see LI.FI docs. 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 LI.FI 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 LI.FI and CCTP docs?
LI.FI: LI.FI Docs. CCTP: Circle CCTP Docs. Live rate comparison: rates.gg.
Official sources
- LI.FI docs: LI.FI Docs
- LI.FI app: li.fi
- LI.FI — What LI.FI provides: docs.li.fi/introduction/introduction
- LI.FI — Product stack: docs.li.fi/introduction/product-stack
- LI.FI — API overview: docs.li.fi/api-reference/introduction
- 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 LI.FI 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.