Circle Gateway is a smart-contract and attestation system from Circle that gives users a single USDC balance spendable across supported chains in under 500 milliseconds, per Circle's Gateway documentation. It went live on mainnet in August 2025 with seven chains and has since expanded: Circle's Gateway supported blockchains reference now lists Arbitrum, Arc, Avalanche, Base, Ethereum, HyperEVM, OP, Polygon PoS, Sei, Solana, Sonic, Unichain and World Chain. Gateway is one rail in a broader multi-rail settlement stack that also includes burn-and-mint protocols, generalized messaging layers, and intent-based solver networks.
​

USDC supply sits at roughly $73.4B as of September 15, 2026, per DefiLlama, and Circle's stated goal with Gateway is to make that supply behave like one balance rather than fragments scattered across chains. This article explains how Gateway works, where it fits in the wider settlement landscape, how it compares to CCTP V2, lock-and-mint bridges, and intent solvers, and which integration path makes sense for a given use case.
​

Circle Gateway is a non-custodial smart-contract system paired with an offchain attestation service that lets a user deposit USDC once and access it as a unified balance on any supported chain. Circle's Gateway documentation describes it as fully permissionless, with transfers minting in under 500 ms once a balance is established and a 7-day trustless withdrawal option that does not depend on Circle. Only USDC is supported. It is not a bridge or a wrapped-asset system.
​

The mechanism centers on a Gateway Wallet contract, a burn-intent signature from the user, and a signed attestation from Circle's API. Once an intent is attested, USDC can be minted on the destination chain in the next block while the equivalent is burned from the unified balance on the source chain. Circle's launch announcement is on the Circle blog, and developer documentation lives at Circle Developers.
​

Gateway launched on mainnet in August 2025 with seven supported chains and a sub-500 millisecond transfer target. USDC remains the only supported asset and the system is permissionless to integrate, per Circle's Gateway documentation. The chain list has grown since launch and the fee schedule is now published as a standing one rather than an early-access one, so both are worth reading from source before you size an integration.

Gateway works in three steps: deposit USDC into a Gateway Wallet contract, sign a burn intent when spending on a destination chain, and submit Circle's signed attestation to a Gateway Minter contract that mints USDC on the destination while burning it from the unified balance on the source. The flow keeps total USDC supply constant and never holds funds custodially.
​

A user sends USDC into the Gateway Wallet contract on any supported chain. Circle's offchain service observes the deposit, waits for source-chain finality, then credits the user's unified balance. The contract is non-custodial: withdrawals can always be initiated by the depositor and complete trustlessly after a 7-day window, even if Circle's attestation service is down.
​

When the user wants to spend USDC on a destination chain, the integrating application asks the user to sign a burn intent message specifying the destination, amount, and recipient. The application submits this intent to Circle's Gateway API, which returns a signed attestation, provided the unified balance covers the amount. Circle's Gateway documentation puts the end-to-end mint at under 500 ms once the balance exists.
​

The application or a paymaster submits the attestation to a Gateway Minter contract on the destination chain. The Minter mints USDC for the recipient, and Circle burns the matching amount from the user's unified balance on the source chain. From the user's perspective, the USDC simply appears on the destination chain in the next block.
​

Cross-chain USDC movement is no longer served by one rail. Gateway is the USDC unified-balance rail in a stack that also includes Circle's CCTP V2 for burn-and-mint transfers, generalized messaging layers like Hyperlane and LayerZero V2 for arbitrary cross-chain data, and intent-based solver networks like Eco Routes and Across that source liquidity just in time across chains and assets.
​

Each rail optimizes for a different constraint. CCTP V2 is the canonical burn-and-mint primitive for USDC and is widely used as a settlement leg inside other systems. Messaging layers like Hyperlane and LayerZero V2 move arbitrary payloads, not just stablecoin value. Solver networks like Across and Eco Routes let users express an intent on chain A and have a competitive solver fulfill it on chain B, often fronting capital so the user does not wait for source finality. Gateway sits between these: it is USDC-only, pre-funded by the user into a unified balance, and optimized for sub-second access without solver risk or wrapped tokens.
​

A simple decision rule. If a user already holds USDC and wants near-instant access on another supported chain without depending on a third-party filler, Gateway fits. If a developer needs canonical USDC settlement without pre-funding, CCTP V2 fits. If the transfer involves a non-USDC asset, an unsupported chain, or a contract action on the destination, an intent solver or messaging layer is usually the right rail. Gateway isn't a bridge replacement. It's the USDC rail in a multi-rail settlement stack where intent solvers, messaging layers, and burn-and-mint each do what they're best at.
​

The four rail categories differ along latency, capital model, trust assumptions, and asset scope. The table below summarizes the differences using publicly documented behavior. Latency figures reflect attestation or fill time on Ethereum mainnet and L2s; finality on slower source chains can extend totals for any burn-and-mint design.

Gateway is aimed at operators who already hold USDC and need to spend it across many chains without juggling per-chain inventory. The four common categories are payment service providers, exchanges, wallets, and DeFi market makers or solvers. Each gets a different operational benefit, but the shared mechanic is the same: deposit once, spend anywhere supported, with no rebalancing.
​

PSPs and fiat-to-crypto onramps historically pre-fund USDC across every chain they support, which ties up working capital and adds rebalancing complexity. With Gateway, a single deposit serves every supported chain, so a user buying USDC for delivery on Base or Polygon draws from the same pool the provider holds on Ethereum.
​

Exchanges advertise instant USDC withdrawals on multiple chains, which forces them to hold hot-wallet inventory on each. Gateway lets an exchange satisfy withdrawal requests from a unified balance and shrink the per-chain hot-wallet footprint. CCTP V2 covers cases where the exchange would rather burn-and-mint just in time without keeping a pre-funded balance.
​

Wallets can show users a single chain-agnostic USDC balance and let them send or swap on any supported chain in one tap. This is the most user-visible Gateway use case and the closest expression of the chain-abstraction thesis: the user stops thinking about which chain they are on.
​

Solvers in intent networks like Eco Routes and Across already front USDC liquidity across chains. Gateway gives those solvers a way to hold a single USDC inventory and pull from it on demand, instead of pre-positioning capital on every chain they cover. Solver economics improve when idle inventory drops.
​

Eco operates an intent-based stablecoin liquidity layer where solvers compete to fulfill user transfers. Eco Routes can use Gateway as the USDC settlement leg on supported chains while solvers handle non-USDC assets, unsupported chains, and contract-action intents. The two systems are complementary: Gateway gives solvers a unified USDC inventory, and Eco gives users an asset-agnostic intent surface.
​

For builders, this means choosing the rail per leg rather than per product. A USDC-to-USDC transfer between two Gateway chains can settle through Gateway. A USDC-to-ETH swap landing on an unsupported chain can route through an Eco solver that uses Gateway internally for the USDC portion. More context on the intent model is in and What is Eco Routes?.
​

Integrating Gateway involves three contract and API touchpoints: the Gateway Wallet contract for deposits and withdrawals, the burn-intent message that the user signs, and the attestation API that returns a signed payload for the destination-chain Gateway Minter. Circle's documentation walks through a unified balance flow end to end at Circle Developers.
​

Integration is permissionless. Builders do not need a partnership agreement with Circle to ship a Gateway-backed feature, which is consistent with how CCTP V2 is exposed. Reference implementations from Circle cover EVM signing, attestation request payloads, and Minter contract calls, and Circle publishes ABI files for both the Wallet and Minter contracts. Useful starting points:

Gateway is non-custodial in the sense that the Gateway Wallet contract only releases USDC against a user signature or a trustless withdrawal request. Spending across chains requires both a user-signed burn intent and a Circle-signed attestation. If the attestation service is unavailable, the user can still withdraw after the 7-day trustless window without Circle's cooperation.
​

The trust assumptions are therefore the same as other Circle attestation-backed products: users rely on Circle to attest accurately and to maintain liveness for fast transfers, but never to take custody. The fallback withdrawal is the mechanism that bounds liveness risk. As with any system that depends on smart contracts and offchain services, builders should review Circle's published documentation and contract source before integration.
​

Circle's Gateway fees reference publishes two components. The crosschain transfer fee is 0.005%, which is 0.5 basis points, deducted from the unified balance at the time of burn, and same-chain withdrawals do not incur it. On top of that each burn intent carries a fixed gas fee in USDC that varies by source chain: $1.00 on Ethereum, $0.02 on Avalanche, $0.05 on HyperEVM, $0.01 on Arbitrum, Base and Sonic, $0.15 on Solana, and fractions of a cent on OP, Polygon PoS, Sei, Unichain and Arc. The source chain you burn from therefore matters more to the bill than the percentage fee does on small tickets.
​

For high-throughput integrators, the operational cost story is broader than the basis-point fee. Gateway removes the need to hold per-chain working capital, so the relevant cost comparison includes the carrying cost of idle inventory under the status quo. For one-off transfers without a pre-funded balance, CCTP V2 or a solver network may be cheaper because no deposit is required upfront.
​

Common questions about Gateway focus on whether it is a bridge, how it differs from CCTP, which chains it supports, and whether it is custodial. The short answers: Gateway is not a bridge, it is complementary to CCTP rather than a replacement, it supports thirteen chains on Circle's Gateway supported blockchains reference, and it is non-custodial with a 7-day trustless withdrawal fallback.
​

Is Circle Gateway a bridge?
​

No. A bridge typically locks an asset on chain A and mints a wrapped representation on chain B, or uses a liquidity pool to deliver a different token on the destination. Gateway uses native USDC on every chain, burns and mints against a unified balance, and never produces wrapped USDC.
​

What is the difference between Gateway and CCTP?
​

Both are Circle products that move native USDC across chains, but the capital model differs. CCTP V2 is a just-in-time burn-and-mint protocol used when a user wants to move a specific amount from one chain to another. Gateway is a pre-funded unified balance model used when a user or treasury wants on-demand access on any supported chain without sending a transfer first.
​

Which chains does Gateway support?
​

Per Circle's Gateway supported blockchains reference, Gateway supports Arbitrum, Arc, Avalanche, Base, Ethereum, HyperEVM, OP, Polygon PoS, Sei, Solana, Sonic, Unichain and World Chain. Nanopayments are supported on all of those except Solana. The list grows, so read it from Circle rather than from any secondary summary, including this one.
​

Is Gateway custodial?
​

No. The Gateway Wallet contract is non-custodial. USDC only moves when the user signs a burn intent or initiates a trustless withdrawal. Even if Circle's attestation service goes offline, the user can withdraw their full balance after a 7-day window without Circle's involvement.
​

Does Gateway support assets other than USDC?
​

Not at launch. Gateway is USDC-only and Circle has not publicly committed to adding other assets. Builders needing multi-asset cross-chain settlement typically combine Gateway for the USDC leg with intent solvers or messaging layers for the rest.
​

How fast is Gateway in practice?
​

Circle's Gateway documentation puts a transfer at under 500 ms once the unified balance is established. The part people underestimate is establishing it: Circle's Gateway supported blockchains reference lists the block confirmations Gateway waits for before crediting a deposit, and on Arbitrum that is roughly 65 Ethereum blocks, about 13 to 19 minutes. Gateway is instant to spend and not instant to fund, which is exactly why it suits pre-funded treasuries rather than one-off transfers.
​

For deeper context on the rails Gateway sits alongside, the chain-abstraction thesis it implements, and the stablecoin infrastructure landscape, the articles below cover the adjacent topics in more detail. They are useful before deciding which rail or combination of rails to integrate.