On September 2nd, Circle announced that its cross-chain transfer protocol CCTP has begun to support the native cross-chain transfer of the euro stablecoin EURC. The first networks to support this feature are Ethereum and Base. Developers can use the same production-grade interoperability infrastructure as with USDC to move EURC between these two chains. It's important to clarify that this announcement specifically confirms support between Ethereum and Base; it does not imply that EURC has already covered all blockchains through CCTP.
CCTP adopts a method of "destroys the source chain and creates on the target chain." After a user initiates a transfer on the source chain, the corresponding EURC is destroyed; after the service confirmation event on Circle, an equal amount of native EURC is created on the target chain. This approach differs from the traditional method of locking tokens in a bridge contract and then issuing a packaged certificate, as the target chain receives native assets issued by Circle, thereby reducing the fragmentation of liquidity caused by multiple packaged versions of the same stable coin.
A set of cross-chain infrastructure has begun to support two types of currencies.
CCTP mainly served USDC before. With the addition of EURC, developers can use a unified system to handle US dollar and euro stablecoins, reducing the costs associated with selecting different bridges, maintaining contracts, and dealing with various trust models. For multi-currency wallets, cross-border settlements, on-chain foreign exchange, and corporate fund management, such a unified interface is more practical than adding new token trading pairs.
Destruction and re-creation do not mean that the cross-chain process is risk-free. Transfers still rely on message passing, proof verification, target address, and application integration. Circle reminds clearly that CCTP is a non-managed cross-chain messaging infrastructure, not a payment, brokerage, or investment service; transfers are irreversible, and assets sent to the wrong address cannot be recovered by the service provider. Developers need to verify the chain, address, and amount in the interface, and provide a second confirmation for large-value transfers.
The advantage of native liquidity is that different chains do not need to maintain their own reserves of EURC. As the supply on the source chain decreases and the supply on the target chain increases, the total issuance remains consistent in theory. This facilitates unified identification of assets by exchanges, lending protocols, and payment applications. However, the uniformity at the protocol level does not automatically create market depth; the actual usage costs are still determined by the trading volume on Base, market-making activities, and the channels for redeeming with fiat currencies on Ethereum.
EURC is denominated in euros, providing European enterprises, traders, and global users with an on-chain settlement unit that does not require the use of the US dollar. Enterprises can more naturally match their euro revenues and expenditures, reducing unnecessary exchange rate exposures. At the same time, stablecoins still carry risks associated with issuers, reserves, smart contracts, and regulation; price stability is a design goal, but it is not an absolute guarantee under any market conditions.
After the cross-chain experience is simplified, the application's responsibilities become even greater.
When the underlying interfaces become unified, it becomes easier for wallets and applications to present cross-chain options to users. However, the more "one-click" the process is, the more important it is to clearly display the source chain, target chain, fees, estimated time, and the assets that will ultimately be received. Users should not send EURC to unsupported contracts without being aware of it, nor should they confuse test networks, counterfeit tokens, or third-party packaged versions.
For the DeFi protocol, supporting CCTP is merely a technical prerequisite. Whether to accept EURC as collateral, for trading, or for settlement also requires contract auditing, oracle evaluation, liquidity analysis, and governance processes. Application parties also need to handle exceptional situations such as temporary service unavailability, message delays, and chain reorganizations, and cannot assume that each transfer will be completed instantaneously.
Cross-chain transfers are not equivalent to foreign exchange conversions. When CCTP moves one EURC from one chain to another, the unit of asset valuation remains the euro; if users wish to convert between EURC and USDC, they still need a trading platform, quotes, and liquidity. A unified infrastructure can make it easier for these two assets to be used within the same application, but it will not automatically eliminate price fluctuations and conversion costs between euros and dollars.
From the perspective of supply auditing, destruction and creation events should correspond on both chains, allowing applications to track the transfer status accordingly. Developers need to prevent duplicate processing, incorrect retries, and premature accounting when the creation on the target chain has not yet been completed. For corporate financial systems, the final state on the chain must also be reconciled with internal ledgers, especially in cases of delays that occur across days or during peak periods.
Security boundaries also include official domain names and contract addresses. After the new feature is launched, phishing websites across chains often take advantage of hot topics to induce authorization. Users should enter through the Circle documentation or audited applications, first conduct small-scale tests, and check the target chain and tokens displayed in their wallets. The protocol security of CCTP cannot reverse a single incorrect signature on behalf of the user.
Circle mentioned that in the future, more assets and capabilities will be added to this cross-chain trust layer. However, the fact that has already been implemented this time is that EURC can be transferred natively between Ethereum and Base. Any descriptions regarding more chains or assets still fall under subsequent plans. Developers should refer to the official support list and the latest documentation before launching the product.
This expansion reflects that the focus of competition in stablecoin infrastructure is changing. In the early stages, the competition was about which chains would issue these coins, but in the next phase, the focus shifts to whether the same asset can maintain a unified supply, clear identity, and accessible liquidity across multiple chains. CCTP allows EURC to reuse the already operational burn-and-mint mechanism of USDC, which lowers the barriers to integration. Whether this will significantly increase the use of such coins on the euro chain still depends on factors such as transaction volume, corporate demand, and compliance requirements, rather than the cross-chain functionality itself.
