Enso vs. CCTP
Rift Research
Last updated
TLDR: Enso is a DeFi action and shortcut layer. CCTP is Circle’s native USDC burn-and-mint protocol. Consider Enso when you need multi-step DeFi intents, not only a simple swap. Consider CCTP when you are moving pure USDC to USDC between supported chains. Confirm the live winner on rates.gg.
What each protocol is
Enso. Enso is a unified DeFi API. The Route API finds a path into a destination token, LP or vault. The Bundle API composes ordered actions (swap, lend, borrow, deposit) into one transaction. Enso constructs transaction data for the integrating product to present for signing. The signing flow and underlying protocols determine permissions and custody assumptions. Official docs: Enso Docs. App: enso.finance.
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 | Enso | CCTP |
|---|---|---|
| Role | DeFi action and shortcut layer | Circle native USDC burn-and-mint |
| Fee | Depends on the composed route and underlying protocols | Check the applicable CCTP version and route: transfer fees and network gas depend on transfer mode and chain |
| Coverage | Multi-chain DeFi primitives connected through Enso integrations | Circle-supported USDC domains (Ethereum, L2s, Solana, Aptos and others) |
| Settlement | Atomic bundled transaction when using Bundle; otherwise the returned route tx | Native USDC (burn source, mint destination) |
| Trust model | Enso router / wallet adapters plus each underlying protocol | Circle attestation / issuer |
| Good fit for | Multi-step DeFi intents, not only a simple swap | Native USDC transfers between supported domains |
| Docs | Enso Docs | Circle CCTP Docs |
Where each fits
Enso may fit when:
- The job is swap-plus-deposit, zap, or another multi-step action
- You want Enso to build the calldata while you keep the wallet UX
- A single-hop bridge or AMM swap is not enough
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. Enso 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 Enso when you need multi-step DeFi intents, not only a simple swap.
- 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, Enso or CCTP?
Neither has a universal price advantage. Enso: Depends on the composed route and underlying protocols. 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 Enso 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 Enso and CCTP docs?
Enso: Enso Docs. CCTP: Circle CCTP Docs. Live rate comparison: rates.gg.
Official sources
- Enso docs: Enso Docs
- Enso app: enso.finance
- Enso — Developer home: docs.enso.build/home
- Enso — Use cases: docs.enso.build/pages/use-cases
- Enso — API: api.enso.finance/api
- 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 Enso 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.