Circle Gateway adds EURC and cirBTC; fees and chain coverage differ

Circle expanded Gateway to EURC and cirBTC on October 23, 2026, announcing separate unified balances for its euro stablecoin and wrapped-bitcoin token. The published scope differs: six chains for EURC, two for cirBTC. Builders also need to distinguish the advertised access time from deposit finality, withdrawal delays and the full transfer bill.

The expansion is a software capability announcement, rather than proof of customer adoption or a guaranteed saving. CoinAbout reconstructed the asset-and-chain coverage and the fee arithmetic, then compared the launch with Circle's product disclosures and its separate Solana pre-mint notice. The result is a more specific picture than a promise of instant movement everywhere.

The support map is asset-specific

Circle's October 23 Gateway announcement lists EURC on Arc, Avalanche, Base, Ethereum, Solana and World Chain. It lists cirBTC on Arc and Ethereum. These are the networks named for the expansion; they do not establish that either asset supports every workflow on every blockchain.

The simplest way to read that list is as two rows. EURC has six named destinations. cirBTC has two, both already present in the EURC row. Together that makes eight asset-and-chain combinations across six distinct chains. Counting them as eight different networks would double-count Arc and Ethereum.

It also would be wrong to carry EURC's Solana support into the cirBTC row. Support attaches to the asset, network and function being described. A platform can offer one token on a chain without offering every other token there, even when the same APIs or software kit provide the integration surface.

Circle describes a unified balance for each asset. That does not merge a euro-denominated balance, a dollar-denominated balance and bitcoin exposure into a single interchangeable holding. Using funds on another supported chain is different from exchanging EURC for USDC or acquiring native bitcoin. A separate conversion would require its own terms and price.

The fee calculation needs a unit

Outside Arc, the launch quotes a Gateway percentage fee of one basis point for EURC and cirBTC, compared with 0.5 basis points for USDC. It describes an initial waiver of the Gateway fees for the two newly added assets on Arc. These are announced fee terms, not a complete quote for every route or a commitment that a waiver lasts indefinitely.

One basis point is 0.01%, or one ten-thousandth of an amount. Applied only to the percentage component, a hypothetical transfer of 1 million EURC at that rate gives 100 EURC. The same arithmetic on 10 cirBTC gives 0.001 cirBTC. Neither example supplies an exchange rate or assigns today's dollar value to the tokens.

At the quoted 0.5-basis-point USDC rate, a hypothetical 1 million USDC produces a 50 USDC percentage component. The announced rate for EURC and cirBTC is therefore twice the USDC rate outside Arc, with a difference of 0.5 basis points. That ratio concerns rates; it does not make 100 EURC economically comparable to 50 USDC without a currency conversion.

The Gateway product page's fee explanation separately describes a base fee covering the source-chain burn's gas cost. That means the percentage worksheet is a component calculation, rather than an all-in bill. A decision still needs the applicable route, gas-related charges, deposit costs and any other disclosed fees.

An Arc waiver of a Gateway fee should likewise not be promoted into a claim that every blockchain operation is free. Removing one price component does not remove the resource cost of every step in a workflow. The relevant comparison is the total charge for the exact action the user intends to complete.

The speed claim starts after a prerequisite

Circle describes crosschain access in under 500 milliseconds after deposit finalization, with a warning that time estimates are not guaranteed. The words after deposit finalization define the starting line. They do not describe the full elapsed time from deciding to fund an account to having spendable funds on another network.

A useful timing record separates submitting the deposit, reaching the required finality, receiving access through Gateway and completing the intended destination action. A fast step in the middle does not establish that all other steps take the same amount of time. Network conditions and the chosen route can affect the result.

That distinction matters for a payments company deciding when inventory must be ready. The product may reduce the need to keep separate funded pools on every chain. It does not follow that the firm can ignore the initial funding interval, service availability or a customer's deadline. Those dependencies still belong in its operating plan.

CoinAbout has not sent a transaction or timed the service. The sub-second number remains Circle's conditional product claim. A measured result would need a defined asset, source and destination, finality rule and observation method. A company announcement alone cannot supply that independent performance evidence.

The withdrawal fallback uses a different clock

The product FAQ says normal rapid access requires a user signature and a Gateway attestation. It describes a permissionless withdrawal path that completes after a seven-day period if the API is unavailable. That fallback and the normal access path solve different operational problems.

The existence of a withdrawal route can be valuable without making it suitable for a payment due tomorrow. A business that depends on rapid settlement still needs to consider what happens when that path is unavailable. A fallback measured in days should not be described with the normal path's millisecond timing.

There is also a documentation limit to resolve before deployment. Although the launch and product headline describe additional assets, generic disclosure text on the pages still includes the words “USDC only.” Those words do not erase the specific announcement, but the mixed wording leaves a reason to confirm the exact feature and applicable terms before relying on it.

Solana pre-minting is not new customer demand

In a separate October 23 notice, Circle says it deployed a pre-mint address for Gateway EURC on Solana. The notice explains that balances at such internal addresses are outside circulation until Circle authorizes release to a user's wallet. It also warns customers against sending EURC to those addresses.

That distinction changes how a reader should interpret an infrastructure update. Creating an operational address is not, by itself, evidence that a customer bought tokens, that circulating supply increased by its entire balance or that payment demand rose. Those claims would require additional, dated supply or transaction evidence.

This report has not queried that address, counted its tokens or audited supply. It therefore gives no new on-chain balance or circulation total. The document finding is the separation between internal pre-minted inventory and authorized public release. Treating both as customer circulation would answer the wrong measurement question.

The investment case remains a separate question

The strongest operational case for unified balances is reducing inventory fragmentation while preserving asset identity. The counterargument is that a convenient balance display can hide dependencies on finality, attestations, software availability and the underlying issuer. The expansion does not eliminate those dependencies simply by putting several assets behind familiar interfaces.

cirBTC also remains wrapped bitcoin issued by Circle, rather than native BTC on the Bitcoin network. Readers using CoinAbout's Bitcoin page or EURC page should distinguish the underlying market asset from the specific token and transfer service being discussed.

Evidence that would strengthen the announcement includes consistent feature documentation and actual results for the claimed routes, with total fees and start-to-finish timing disclosed. Until then, the named support map and component calculations are more defensible than claims of universal availability or proven savings. Issuer, smart-contract, liquidity and operational risks remain; a new integration is not a guarantee of safety or returns.