Make Your Token Interoperable with CCTP

Circle explains how its Cross-Chain Transfer Protocol (CCTP) extends its burn-and-mint transfer model beyond USDC to issuer-operated ERC-20 tokens, enabling a single economic asset identity across supported EVM chains. On Arc Testnet, developers can either deploy a new native CrossChainToken, whose shared token identity is determined by a deployer address and salt, or connect an existing issuer-controlled ERC-20 through custom configuration; both approaches use Circle’s message and Iris attestation infrastructure while retaining issuer control over roles, rate limits, and transfer caps. Transfers burn tokens on the source chain, obtain an Iris attestation, and mint corresponding tokens on the destination, with optional forwarding to complete delivery without destination-chain gas. The guidance emphasizes matching token decimals, establishing trusted domains between chains, approving each token’s manager, checking live transfer fees, and setting limits during deployment to avoid blocked transfers. Circle also notes that Arc uses USDC for gas, that Arc mainnet and testnet are offered as software infrastructure without regulatory approval or financial services, and that cross-chain transfers are irreversible and subject to blockchain, smart-contract, bridge, and third-party asset risks.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.