NEAR Intents vs. CCTP
Rift Research
Last updated
TLDR: NEAR Intents is a multichain intent and solver network. CCTP is Circle’s native USDC burn-and-mint protocol. Consider NEAR Intents when you need unusual pairs, non-EVM routes, or solver-sourced liquidity. Consider CCTP when you are moving pure USDC to USDC between supported chains. Confirm the live winner on rates.gg.
What each protocol is
NEAR Intents. NEAR Intents is a multichain intent protocol. You specify the outcome (asset in, asset out, destination). Market makers compete to fill it. The verifier contract settles intent batches on NEAR. Cross-chain deposits and withdrawals use token bridges, with their own settlement and refund conditions. Official docs: NEAR Intents Docs. App: near-intents.org.
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 | NEAR Intents | CCTP |
|---|---|---|
| Role | Multichain intent + solver network | Circle native USDC burn-and-mint |
| Fee | Solver spread set in the winning quote | Check the applicable CCTP version and route: transfer fees and network gas depend on transfer mode and chain |
| Coverage | Bitcoin, EVM chains, Solana, NEAR, TON, Sui, Stellar and other listed assets | Circle-supported USDC domains (Ethereum, L2s, Solana, Aptos and others) |
| Settlement | Atomic via the intents verifier on NEAR | Native USDC (burn source, mint destination) |
| Trust model | Verifier contract on NEAR, solver liquidity, and the token bridges used for deposits and withdrawals | Circle attestation / issuer |
| Good fit for | Unusual pairs, non-EVM routes, and solver-sourced liquidity | Native USDC transfers between supported domains |
| Docs | NEAR Intents Docs | Circle CCTP Docs |
Where each fits
NEAR Intents may fit when:
- The pair or chain sits outside most EVM-only aggregators
- You want solvers competing on a signed intent
- Native settlement across non-EVM ecosystems matters
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. NEAR Intents 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 NEAR Intents when you need unusual pairs, non-EVM routes, or solver-sourced liquidity.
- 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, NEAR Intents or CCTP?
Neither has a universal price advantage. NEAR Intents: Solver spread set in the winning quote. 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 NEAR Intents 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 NEAR Intents and CCTP docs?
NEAR Intents: NEAR Intents Docs. CCTP: Circle CCTP Docs. Live rate comparison: rates.gg.
Official sources
- NEAR Intents docs: NEAR Intents Docs
- NEAR Intents app: near-intents.org
- NEAR Intents — What are intents?: docs.near-intents.org/getting-started/what-are-intents
- NEAR Intents — NEAR chain-abstraction overview: docs.near.org/chain-abstraction/intents/overview
- NEAR Intents — 1-Click Swap API: docs.near-intents.org/
- 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 NEAR Intents 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.