Key Highlights
- Circle has expanded its Cross-Chain Transfer Protocol (CCTP) to support native transfers of EURC, in addition to USDC.
- Developers can use a single integration to enable cross-chain transfers for both EURC and USDC.
- The expanded CCTP uses Circle’s existing message-passing infrastructure and Iris attestation service to verify cross-chain transfers.
Circle, a global financial technology company, has expanded its Cross-Chain Transfer Protocol, known as CCTP, to support native transfers of EURC in addition to USDC. The update was announced by Circle Developer on September 2, 2026.
According to the official announcement on September 2, CCTP now extends Circle’s cross-chain infrastructure to native EURC transfers. Developers can use a single integration for both assets.
The announcement also notes that, previously, multichain availability required separate bridge providers, custom integrations, and differing trust models, resulting in duplicated infrastructure and operational complexity.
EURC transfers begin on Ethereum and Base using the burn-and-mint model already applied to USDC: the token is burned on the source chain and minted on the destination, so each chain holds native EURC. This unifies liquidity. Existing USDC burn-and-mint functionality remains unchanged. More assets and capabilities are coming soon.
Technical approach to the announcement
A Circle blog post detailed the technical approach. CCTP for non-USDC assets operates as a smart contract layer built on the existing CCTP framework. It enables permissionless cross-chain bridging of third-party assets by reusing CCTP’s message-passing infrastructure and the Iris attestation service. Assets move across blockchains under the same attestation model used for USDC transfers.
Tokens already registered with CCTP for non-USDC assets, including EURC, can be transferred without additional registration steps by the user or integrator. Wallets, decentralized exchanges, bridge aggregators, and other applications that move non-USDC assets between blockchains can integrate the service directly.
Technical differences between CCTP and Non-USDC support
The Circle documentation outlines several distinctions between standard CCTP and the non-USDC extension.
Standard CCTP is limited to USDC and uses the TokenMessengerV2 entry contract. Fees are deducted from the transferred amount, and forwarding is compulsory when the protocol is used.
CCTP for non-USDC assets covers EURC and any registered ERC-20 token. It uses the CrossChainTokenService entry contract. Fees are paid in the native gas token of the source blockchain. Forwarding is optional and can be requested at the time a quote is obtained.
Both versions rely on the Iris attestation service. Hooks are supported in both cases, with the non-USDC version allowing atomic on-arrival execution.
Earlier integration on Cronos
The expansion follows an earlier deployment on the Cronos network. According to the official announcement, on June 29, Cronos became the first blockchain to launch native USDC, native EURC, and Circle’s Cross-Chain Transfer Protocol at the same time. That launch provided users and developers on Cronos with access to both U.S. dollar- and euro-denominated regulated stablecoins alongside native cross-chain settlement.
Circle’s latest announcement expands CCTP’s support for non-USDC assets, with EURC transfers initially available between Ethereum and Base.
Developers seeking to implement the expanded asset support can access documentation at the Circle developers portal under the CCTP section for expanded assets. The protocol continues to rely on the existing Iris attestation service for message verification across supported chains.
Also Read: Robinhood Chain Revenue Hits New All-Time High With $3.8M Daily Fee
