Circle Expands CCTP to Support Custom ERC-20 Tokens on Arc
Circle has expanded its Cross-Chain Transfer Protocol (CCTP) to support issuer-operated ERC-20 tokens on its Arc blockchain, allowing developers to transfer assets between supported networks without relying on separate bridges or wrapped tokens.
In an October 30 developer announcement, Circle outlined how issuers can connect existing tokens or create new crosschain assets using the same messaging and attestation infrastructure developed for USDC transfers.
On October 30, Circle announced CCTP expansion to support issuer-operated ERC-20 tokens on Arc.
The update follows prior launches of EURC and cirBTC, extending cross-chain infrastructure to third‑party assets.
Circle launched Arc mainnet September 16, then released developer walkthrough for testing native cross‑chain tokens.
Explaining the purpose of the expansion, Circle said, “Interoperability means the same economic asset can move to the chain where the application actually runs, under one bridge identity integrators can rely on.”
The functionality is designed for applications handling payments, collateral, tokenized real-world assets and treasury operations across multiple networks.
How CCTP Transfers Tokens Across Blockchains
CCTP uses a burn-and-mint mechanism to move assets between supported blockchains. Instead of locking tokens on one network and issuing wrapped versions on another, the protocol burns the original tokens and mints corresponding tokens on the destination chain.
Circle described the process in its announcement, stating, “CCTP moves value by burning on the source and minting on the destination against an attested message.”
Under this process, the source blockchain burns the tokens and generates a message. Circle’s Iris service verifies the transaction and provides an attestation. The destination network then uses the verified message to authorize the corresponding mint.
For non-USDC assets, transfers are handled through Circle’s CrossChainTokenService and a dedicated manager for each token, rather than the TokenMessengerV2 contract used for standard USDC transfers.
Circle’s latest update extends this infrastructure to third-party tokens whose issuers control the underlying contracts. The company had previously expanded its crosschain infrastructure to support EURC and cirBTC across selected blockchain routes.
Two Ways to Connect ERC-20 Tokens
Circle has outlined two integration methods depending on whether developers are launching a new token or already operate an existing ERC-20 asset.
For new projects, developers can deploy a native CrossChainToken through Arc’s CrossChainTokenService. The deployment creates both the token contract and a dedicated manager responsible for crosschain operations.
A shared token identifier is generated using the deployer’s wallet address and a selected salt value. Developers can reuse these details when deploying the corresponding token on another supported blockchain.
Existing token issuers can instead register their ERC-20 assets as custom CCTP tokens without replacing their original contracts. This requires configuring the token on every blockchain involved in the transfer route, including the necessary burn-and-mint permissions.
Issuers also retain control over ownership, operator and pauser roles, transaction rate limits and maximum transfer amounts.
Circle highlighted these responsibilities, stating, “You set the owner, operator, pauser, rate limits, and max transfer.”
Both methods require matching token decimals across networks and compatible configurations between the services handling transfers.
Forwarding Service Handles Destination Transfers
Developers can complete destination transactions themselves or use Circle’s forwarding service to automate delivery.
The service can submit destination transactions without requiring recipients to pay gas fees on the receiving blockchain. Developers must include the forwarding option in the initial Iris fee quote.
Circle’s documentation also explains that transfer fees can be paid on the source blockchain. When the required fees are covered separately, recipients receive the full transferred token amount. Actual charges depend on the blockchain pair and the quote obtained before execution.
Arc Expands Its Financial Infrastructure
The CCTP expansion adds another component to Circle’s efforts to develop Arc as infrastructure for financial applications.
Circle launched Arc mainnet on September 16, introducing a Layer 1 blockchain that uses USDC for transaction fees and offers deterministic transaction finality.
Highlighting the network’s design, Circle said, “Arc is built for applications that move value, with fees in USDC and deterministic finality that keeps CCTP attestation timing predictable.”
The latest developer walkthrough focuses on deploying and testing native crosschain tokens on Arc Testnet before moving to production.
Circle recommends that developers review contract addresses, administrative permissions and transfer limits before deploying assets. Issuers must also obtain fresh Iris fee quotes when adding new blockchain routes.
The company has not announced a specific production rollout timeline for the newly documented third-party token integrations.
Disclaimer: The information researched and reported by The Crypto Times is for informational purposes only and is not a substitute for professional financial advice. Investing in crypto assets involves significant risk due to market volatility. Always Do Your Own Research (DYOR) and consult with a qualified Financial Advisor before making any investment decisions.


