Circle CCTP Support

DFNS now moves USDC across chains through Circle's Cross-Chain Transfer Protocol.

Chris Sutton
Chris Sutton
| 6 min read

DFNS now supports cross-chain USDC transfers through Circle’s Cross-Chain Transfer Protocol (CCTP). With a single API call from a source wallet, USDC moves natively from one chain to another and lands in a destination wallet on DFNS, across EVM to EVM, EVM to Solana, and Solana to EVM. There is no third-party bridge, no wrapped assets, no custody intermediary, and no gas or signing required on the destination side. And because it runs on the same platform as every other transaction, each cross-chain move is governed by the same policies and approvals as the rest of an institution’s operations.

The problem: USDC is everywhere, and moving it is manual

USDC is issued natively on many chains, which is a strength until you need the same dollars on a different one. Today, moving USDC across chains usually means leaving the platform: bridging through a third-party interface, holding native gas on the destination chain to claim the funds, accepting a wrapped or locked representation rather than real USDC, and waiting on unpredictable finality. For an institution, that is operational risk, custody exposure to a bridge, and a workflow that cannot be governed or automated alongside everything else. Managing balances across chains becomes a manual juggling act.

The solution: native USDC across chains, in one call

DFNS uses Circle’s CCTP, the canonical protocol for moving USDC between chains. CCTP burns USDC on the source chain and mints fresh, native USDC on the destination. There are no wrapped assets and no custody intermediary holding funds in the middle. The dollars that arrive are real USDC, issued by Circle on the destination chain.

DFNS runs this in Circle-forwarded mode, which removes the destination-side burden entirely. You submit one request on the source wallet. DFNS signs and broadcasts the transactions on the source chain. Circle’s attestation service then issues an attestation, and Circle’s Forwarding Service submits the claim on the destination chain from its own keys. The destination wallet is only the recipient address: its keys are never touched, and it needs no native gas to receive the funds.

How DFNS supports it

CCTP is available as a provider on the existing swaps endpoint, alongside Uniswap. A USDC-to-USDC request across two different networks routes through CCTP automatically, with the same quote, commit, and status-polling flow as any other swap.

Under the hood, a transfer is two source-chain transactions followed by an off-chain wait. On EVM, DFNS signs an approval and then a burn through its normal transaction lifecycle. On Solana, the approved step does not exist, so it is a single burn instruction. Once the burn confirms, the destination mint is guaranteed to follow: Circle’s attestation is permanent and the claim is retried until the USDC lands, so a transfer cannot be burned on one side without arriving on the other. DFNS detects the mint on the destination wallet and completes the swap.

You choose the speed per request. Fast settles end to end in roughly 8 to 20 seconds for a small additional fee. Standard waits for source-chain finality, roughly 13 to 19 minutes, with no fast fee. CCTP is 1:1 at the protocol level, so there is no exchange-rate slippage. The only costs are source-chain gas, Circle’s forwarding fee, and the fast fee if you choose Fast, and a slippage tolerance on the request bounds the delivered amount so a transfer fails rather than under-delivering if live fees move.

Governed like every other transaction

This is the part that matters for an institution. Because a cross-chain USDC move runs through the same construct, sign, and broadcast lifecycle as any other DFNS transaction, the burn is subject to the same Policy Engine controls: approval quorums, spending limits, address allowlists, and KYT screening before anything is signed. Which wallets can move USDC, to which chains, and in what size becomes a controlled, auditable decision rather than an action taken on a third-party site outside your controls. Every request also accepts an externalId for idempotency, so a retry never produces a double burn.

One API, one example

No new endpoint. The existing swap endpoints accept a CCTP-routable pair and select the provider internally. To move USDC from an Ethereum wallet to a Solana wallet:

POST /swaps/quotes
{
  "provider": "CIRCLE_CCTP",
  "walletId": "wa-source-eth-...",
  "targetWalletId": "wa-dest-sol-...",
  "sourceAsset": { "kind": "Erc20", "contract": "0xA0b8...eB48", "amount": "1000000000" },
  "targetAsset": { "kind": "Spl", "mint": "EPjFWdd5...TDt1v" },
  "slippageBps": 50,
  "speed": "Fast"
}

The source and destination networks are inferred from the wallets. The response returns the floor amount of USDC delivered after Circle’s fees. Commit with POST /swaps using the quote, then poll for status.

What this unlocks

  • Move USDC across chains without leaving DFNS or touching a third-party bridge.
  • Receive real, native USDC on the destination, not a wrapped or bridged representation.
  • No native gas and no signing on the destination chain.
  • Rebalance treasury across chains, and pay out on whichever chain a counterparty needs.
  • All swaps are policy-aware and are configurable for systems, humans, and agents.
  • Settle in seconds when speed matters, or save the fee on bulk moves when it does not.

Part of a deeper USDC integration with Circle

CCTP is the first step in a deeper USDC integration with Circle. Coming next: minting USDC directly inside DFNS wallets via Circle Mint, and a unified, chain-abstracted USDC balance, so institutions can hold and move dollars across chains as a single balance. Cross-chain movement is the foundation the rest builds on.

Get started

Frequently asked questions

What is the Cross-Chain Transfer Protocol (CCTP)? CCTP is Circle’s protocol for moving USDC natively between blockchains. It burns USDC on the source chain and mints an equivalent amount of fresh, native USDC on the destination, verified by Circle’s attestation service. There is no bridge custody, no wrapped representation, and no counterparty holding funds in the middle.

Is CCTP safe? How does it compare to bridges? CCTP eliminates bridge custody risk — the primary attack vector behind the largest exploits in blockchain history. Because CCTP burns tokens rather than locking them in a contract, there is no pool of assets for an attacker to drain. The Ronin, Wormhole, and Nomad bridge hacks totaled over $1.1B in losses, all targeting locked custody. CCTP’s burn-and-mint design removes that surface entirely.

Does CCTP require native gas on the destination chain? Not with DFNS. DFNS runs CCTP in Circle-forwarded mode, where Circle’s Forwarding Service submits the destination-chain claim from its own keys. The destination wallet needs no native gas and requires no signing. You submit one request on the source side; DFNS and Circle handle the rest.

How fast is a CCTP transfer through DFNS? DFNS offers two speeds per request. Fast settles end to end in roughly 8 to 20 seconds for a small additional fee. Standard waits for source-chain finality — approximately 13 to 19 minutes — with no fast fee.

Is there exchange-rate slippage on CCTP transfers? No. CCTP is 1:1 at the protocol level. The only costs are source-chain gas, Circle’s forwarding fee, and the fast fee if you choose it. A slippage tolerance on the request bounds the delivered amount so a transfer fails rather than under-delivering if live fees move.

Contact us