Circle Adds Native EURC Transfers Between Ethereum and Base Through CCTP
Mainnet records list both networks. Developers must use the non-USDC contract flow and pay transfer fees in native gas.
Circle added EURC to its Cross-Chain Transfer Protocol on September 2, allowing its euro-denominated stablecoin to move natively between Ethereum and Base. The expansion gives developers a euro transfer route alongside USDC, without converting the asset into dollars to move it between those networks. Circle’s announcement identifies both chains as the initial rollout.
The availability claim is supported by more than a launch post. When checked on September 7, Circle’s mainnet token API returned EURC deployments on domains 0 and 6, the identifiers for Ethereum and Base. That confirms the published deployment inventory; it is not an independently executed transfer or a measure of customer adoption.
The same euro asset, on another network
EURC is destroyed on the sending blockchain and newly issued on the receiving blockchain through a burn-and-mint process. The destination asset remains native EURC rather than a separately wrapped token. Circle says the existing USDC transfer mechanism is unchanged.
This is crosschain movement, not foreign exchange. Moving EURC from Ethereum to Base does not itself exchange euros for dollars, deliver money to a bank account or establish a merchant acceptance network. For a treasury holding euros on one chain and needing them on the other, the useful change is the available transfer path.
Familiar infrastructure, different integration work
Circle’s non-USDC integration documentation describes shared attestation infrastructure but different transaction entry points. A developer must approve the per-token TokenManager and initiate the transfer through CrossChainTokenService. Approving the service contract itself does not work.
The fee treatment also differs: non-USDC transfer fees are paid in the sending chain’s native gas asset, rather than deducted from the transferred stablecoin amount. Automated destination delivery is optional. Applications that do not request forwarding must arrange submission of the destination message.
Those differences matter commercially. Reusing the wider infrastructure does not make a USDC-only integration automatically ready for EURC. A payment or treasury application still needs the correct approval flow, gas funding and destination-delivery handling.
Check the route, not the total chain count
The expanded-assets support page lists EURC as pre-registered and requires bilateral trust between the participating domains. Its broader deployment list should not be read as proof that EURC is available on every CCTP chain.
Circle’s worked EURC example uses Sepolia test networks. Production availability should instead be checked against the mainnet token and route inventory. Neither that inventory nor the announcement establishes a guaranteed transfer time, fee saving or payment volume.