Circle's Gateway Adds cirBTC and EURC, But the 500ms Speed Claim Has an Asterisk

Circle pushed Gateway past USDC on October 23, adding cirBTC and EURC to its cross-chain balance service. Developers get one interface for three assets now. That's the headline. The fine print is where things get interesting.

The route matrix is lopsided. cirBTC lives on two chains, Arc and Ethereum. EURC gets six: Arc, Avalanche, Base, Ethereum, Solana and World Chain. A token being live somewhere doesn't make that network a Gateway route, and plenty of teams will read "EURC on Solana" and assume otherwise. They'd be wrong on two counts.

Balances are siloed per asset. Deposit EURC and you get EURC. You don't get cirBTC withdrawals and you don't get dollars. If your app needs a currency swap, that's still your problem. Gateway moves the same asset it received and nothing else.

Then there's the speed number. Circle advertises cross-chain access in under 500 milliseconds. Read the condition attached: that clock starts after a deposit reaches finality on its source chain. First-time depositors are waiting on block times, not half a second. Existing balance holders get the fast path. That's not a lie, but it's the kind of framing that lands in pitch decks without the second sentence attached.

Worth flagging here: deposits sit in noncustodial GatewayWallet escrow contracts, and there's a withdrawal path that skips Circle's API entirely. It takes seven days. Control of funds and speed of access are separate questions, and anyone treating Gateway as a bridge should know which one they're actually answering.

Nanopayments for non-USDC assets stay EVM-only. So EURC on Solana is a Gateway route, not a batched-payment route. Circle's waiving Gateway fees for cirBTC and EURC on Arc at launch, which helps, though it doesn't erase batch settlement costs or smart contract interaction costs.

Who wins? Payments firms serving euro customers across multiple chains, since they can consolidate EURC balances instead of parking reserves on each network. Who gets burned? Teams that architect around an asset-chain combo that isn't in the supported matrix. The attack vector was straightforward: assumption. Check the asset, chain and payment method before you build.