EURC Joins CCTP, but the Route Starts With Two Chains

Circle has shipped native EURC transfers over CCTP between Ethereum and Base, replacing a bridge deposit with an issuer-controlled burn and mint. The September 2 release improves execution for that route: there is no liquidity-pool quote, price impact or wrapped claim to unwind. But it does not remove trust. The transfer depends on Circle’s offchain attestation service, and the launch currently connects only two chains.

How does CCTP move EURC from Ethereum to Base?

CCTP destroys EURC on Ethereum, attests to that burn, then issues the same asset on Base. Consider an order moving €10,000. The sender first approves Ethereum’s EURC contract, at 0x1aBaEA1f7C830bD89Acc67eC4af516284b1bC33c, for the CCTP TokenMessengerV2 contract. The application then calls depositForBurn with 10,000,000,000 token units, because EURC uses six decimals, and sets destination domain 6 for Base. Ethereum is domain 0.

That transaction emits a message containing the source token, amount, recipient, destination and fee ceiling. Circle’s Iris service observes the finalized burn and signs an attestation. A relayer submits the message and signature to Base’s MessageTransmitterV2; TokenMinterV2 then mints native Base EURC at 0x60a3E35Cc302bFA44Cb288Bc5a4F316Fdb1adb42. The recipient gets EURC issued by Circle, not a bridge-branded representation.

• Confirm the source transaction burned exactly 10,000 EURC.
• Decode destination domain 6 and the recipient’s bytes32 value.
• Query the message record until its attestation becomes complete.
• Match the Base MintAndWithdraw event to the burn amount and nonce.

What does an Ethereum-to-Base EURC transfer cost?

Under CCTP’s published schedule, Standard Transfer charges zero protocol basis points, while an Ethereum-origin Fast Transfer costs one basis point. Applied to €10,000, that means a standard fill of €10,000 before network gas, versus €9,999 after a €1 Fast Transfer fee. The published timing benchmark is roughly 15–19 minutes for standard finality and 8–20 seconds for fast attestation.

Those numbers demonstrate the economic advantage over an automated-market-maker bridge: CCTP has no pool depth, spread or price impact. They are not yet a clean EURC service guarantee, however. Circle’s fee reference and public endpoint remain written specifically for USDC, even though the launch says EURC runs on the same production infrastructure. An integrator should obtain an asset-specific quote rather than silently substituting the USDC schedule.

Does EURC on CCTP improve crosschain execution?

Yes, for Ethereum–Base transfers: burning and minting preserves the native asset and removes bridge inventory from the execution path. The trader’s trade-off is clear. Fast settlement sacrifices one basis point under the current Ethereum schedule; standard settlement preserves face value but leaves capital unavailable while finality and attestation complete. Both modes still require source-chain gas, destination execution and confidence in Circle’s signer.

Coverage is the larger limitation. EURC exists natively on six networks—Avalanche, Base, Ethereum, Solana, Stellar and World Chain—but this release initially joins only Ethereum and Base. Circle’s supported-token reference also still omits EURC from its CCTP list, an operational documentation failure builders must absorb.

A live test should start small: record the Ethereum burn time and amount, follow the Iris message status, then verify the Base mint and balance delta. Until the token matrix and EURC fee interface catch up, the transfer mechanism is production-grade, but the integration surface is not.