Community Trust ScoreVerified
Circle published a developer guide on October 30 detailing how issuers can use its Cross-Chain Transfer Protocol (CCTP) infrastructure for ERC-20 tokens other than USDC. The technical documentation outlines the mechanics of burn-and-mint transfers and the specific controls required for issuer-operated assets to function across supported networks.
Technical Mechanics and Attestation
The guide explains that the message and attestation infrastructure behind CCTP can support issuer-operated ERC-20 assets beyond the company’s native stablecoin. For USDC, the established process involves burning tokens on a source network and minting native USDC on a destination network after a verified message is received. Circle states that an analogous route exists for other issuer-operated ERC-20s through the CrossChainTokenService and an associated token manager.
The documentation describes a common token identity across chains, distinguishing this approach from treating wrapped bridge tokens as separate economic instruments. In the described flow, the source contract burns the amount to be transferred and emits a message. Circle’s Iris service then attests to that message. A destination contract receives the attestation and mints the corresponding supply. This controlled burn-and-mint model is presented as a method to keep economic assets coherent across different application environments, addressing fragmentation issues related to liquidity, identity, and accounting.
Deployment Controls and Limitations
The guide covers both native deployment and the configuration of existing custom tokens. Examples within the documentation use Arc Testnet and another supported EVM network. Operators must configure specific parameters, including roles, caps, rate limits, trusted domains, and ownership. The transfer and service details for these non-USDC assets differ from USDC’s TokenMessengerV1 path, requiring developers to confirm the correct contracts and quote fees for specific routes.
Circle clarifies that the Arc demonstration is a testnet walkthrough and does not constitute a promise of universal production support. The source material is a technical guide, not a statement that every ERC-20 can immediately move across every network in production. Circle states it is not the issuer or guarantor of third-party tokens. Developers remain responsible for their own token permissions, legal obligations, and transfer risks.
Before transferring material value, the guide advises developers to test domain trust configuration, fees, rate-limit behavior, decimal consistency, and failure recovery. The documentation notes that moving tokens between venues does not alter cash flows, supply rights, or governance. Interoperability is characterized as infrastructure rather than a direct price catalyst. Institutions may use public, private, or hybrid networks, creating different expectations for access, settlement finality, and oversight.
Frequently Asked Questions
Does the new guide allow all ERC-20 tokens to move across all chains?
No. The guide provides technical instructions for issuer-operated ERC-20s, but Circle states it is not a guarantee of universal production support or that every token can move across every network.
How does the transfer process for non-USDC tokens differ from USDC?
While both use a burn-and-mint model with attestation, non-USDC transfers use CrossChainTokenService and an associated token manager, with different contract details and fee structures than USDC’s TokenMessengerV1 path.
