Skip to main content
CCTP for non-USDC assets is a smart contract layer built on CCTP that enables permissionless crosschain bridging of third-party assets. It reuses CCTP’s message-passing infrastructure and the Iris attestation service to move assets across blockchains using the same attestation model that powers USDC crosschain transfers.
To transfer USDC across blockchains, use standard CCTP. USDC behavior is unchanged.

​
Choose your integration path

The right starting point depends on your relationship to the asset.
  • Transfer a configured token: The token is already configured (including pre-configured tokens like EURC). No configuration required on your end. Typical use cases: wallets, DEXs, bridge aggregators, and any app that moves non-USDC assets between blockchains. See Transfer EURC from Ethereum to Arc.
  • Make your token crosschain: You issue or control the token. Configure it as a custom token to retain full ownership of rate limits, denylist, pause, and upgrades. Circle has no override on custom connections. Typical tokens: fiat-backed stablecoins, RWAs, cirBTC. See Configure a custom token.
  • Bridge an unmanaged asset: You don’t own or operate the token. Configure it as an ownerless connection that starts without an owner and runs on protocol defaults. Typical tokens: wrapped Ether (WETH), wrapped SOL. See Configure an ownerless token.
  • Issue a new token natively crosschain: You have no existing token and want to launch one that is crosschain from day one. The protocol deploys a CrossChainToken ERC-20 and its TokenManager at deterministic addresses through CREATE3, using your deployment wallet and a salt you choose. See Deploy a native crosschain token.

​
Comparison with standard CCTP