Circle says CCTP can now connect non-USDC ERC-20s on Arc
Circle said its Cross-Chain Transfer Protocol can now be used to connect non-USDC ERC-20 tokens, extending the burn-and-mint model beyond its dollar stablecoin and onto Arc, the company’s blockchain for applications that move value. In a blog post published Oct. 30, 2026, Circle described two routes for issuer-operated tokens: deploy a native CrossChainToken through its service or configure an existing ERC-20 as a custom CCTP connection.
Evidence and context
According to Circle, the goal is to let the same economic asset move between supported EVM chains under one bridge identity, rather than forcing every venue to use a separate wrapped token or one-off bridge. The company said Arc is designed for settlement use cases, with fees paid in USDC and deterministic finality intended to make CCTP attestation timing predictable. Circle added that applications can issue or hold inventory on Arc, then move that same asset to another supported chain when settlement, collateral or rebalancing needs change.
Circle said CCTP’s familiar USDC flow remains burn on the source chain and mint native USDC on the destination after an offchain attestation from Iris. For non-USDC assets, the company said the same message and attestation layer now supports ERC-20s, but the transfer path differs from TokenMessengerV2. In the issuer-operated model, Circle said transfers run through CrossChainTokenService and a per-token manager.
The post set out two configurations. A native path is aimed at new tokens designed for CCTP from the start, using deployCrossChainToken on Arc to create the token and manager. A custom path is for an existing ERC-20 that the issuer already operates, using registerCustomToken or a similar setup on each chain in the route. Circle said the issuer controls the owner, operator, pauser, rate limits and maximum transfer settings, and that decimals must match across chains.
Circle also described an end-to-end testnet flow on Arc Testnet. It said developers need a reusable deployer address, USDC for gas and Iris fees, and a token name, symbol, decimals and salt that together define a single tokenId. After deploying the token on Arc, Circle said developers can quote Iris, deploy the remote token on a second chain, approve the per-token manager and call crossChainTransfer. The company said its forwarding option can be included in the fee quote if the sender wants Circle to complete delivery without destination gas.
The company paired the technical note with regulatory and operational disclaimers. Circle said Arc mainnet is an open L1 blockchain launched and offered by Arc Network Services LLC and operated by a permissioned validator set, while Arc testnet is offered by Circle Technology Services, LLC. It also said CCTP is non-custodial, transfers are irreversible, fee estimates are non-binding previews and the service is not a financial, payment or advisory service. Circle said the availability of Arc and CCTP remains subject to change and that users are responsible for compliance with applicable laws.
The new guide follows a series of recent CCTP updates. Circle announced on Sept. 10, 2026 that it is discontinuing support for USDC and CCTP V1 on Noble, and on Aug. 27, 2026 it urged developers to migrate to CCTP V2 ahead of legacy deprecation. CCTP V2 launched on March 11, 2025 and became the canonical version on Nov. 14, 2025, according to Circle’s earlier version-update notice and launch materials.
Circle’s USDC was trading at $0.9995 on Oct. 29, 2026, according to the provided market data, with a reported market capitalization of $71.32 billion. That price was essentially flat over the prior 24 hours.