Arc bridges and onramps: what's confirmed, what's testnet, what's just named — or gone inactive

This is a status page, not a how-to. If you're looking for step-by-step instructions on moving USDC onto Arc, that walkthrough belongs to Meme Central — go there for the click-by-click version. What follows is what is actually confirmed, testnet-only, merely announced, or inactive across the protocols that move USDC into and out of Arc, as of 2 September 2026.

The one bridge mechanism that is unambiguously confirmed: CCTP

Circle's own Cross-Chain Transfer Protocol (CCTP) is the clearest, most verifiable piece of this category. Arc's own developer documentation confirms native CCTP support, with Arc assigned its own CCTP domain (domain 26), and describes the standard burn-and-mint model: USDC is burned on the source chain and minted natively on Arc, rather than represented by a wrapped or bridged token variant. Arc's documentation also highlights that because Arc targets sub-second finality, inbound CCTP transfers can reach attestation faster than transfers into chains that require multiple block confirmations to finalize.

This matters for how you read every other name in this category: CCTP is a Circle-native protocol, documented by Arc itself, with contract-level detail published. That is a different tier of confirmation than a partnership announcement with no technical detail attached, and this guide treats it accordingly.

Circle Gateway: confirmed, and a different thing than a bridge

Circle Gateway is not a bridge in the traditional cross-chain-messaging sense — it's a unified-balance product. The pitch, per Circle's own published material, is that a user or application deposits USDC once and can then access that same balance's liquidity across multiple supported chains without a discrete "bridge and wait" step each time. Circle and Arc have jointly published developer material on combining CCTP and Gateway for consolidating cross-chain USDC into Arc, including a "Unified Balance Kit" for one-integration access to unified USDC flows. This is confirmed, Circle-built, and specifically documented for Arc — the strongest tier of confirmation available in this category alongside CCTP itself.

Third-party interoperability protocols named in connection with Arc

Beyond Circle's own rails, several general-purpose interoperability protocols come up in Arc-adjacent conversation. Read each on its own evidentiary footing — do not assume "interoperability protocol that exists" equals "confirmed to route into Arc."

Axelar has a more specific tie than most: Circle acquired the core Interop Labs development team behind Axelar, announced in Circle's own blog and covered by multiple outlets. That is a corporate and talent acquisition, not itself a public statement that Axelar's messaging protocol routes to Arc mainnet — a meaningfully different claim, and one this guide will not conflate with a shipped bridge integration.

Builds on Arc: Provides cross-chain interoperability messaging; its core development team was acquired by Circle. · Role: Serves · Category: Bridges & Onramps → Interop messaging

LayerZero appears frequently in general commentary about the broader "stablechain" landscape Arc competes in, but no Arc-specific integration, deployed endpoint, or technical documentation was found as of 2 Sep 2026. Not yet confirmed.

Builds on Arc: Provides cross-chain interoperability messaging across EVM and non-EVM chains; not yet confirmed for Arc. · Role: Serves · Category: Bridges & Onramps → Interop messaging

Across Protocol has published commentary discussing Arc as part of the stablechain landscape (alongside Tempo and Plasma) and separately promotes large-USDC-bridge capability generally, but no Arc-specific deployed bridge integration was found as of 2 Sep 2026. Not yet confirmed.

Builds on Arc: Provides fast cross-chain bridging for large USDC transfers; not yet confirmed for Arc. · Role: Serves · Category: Bridges & Onramps → Interop messaging

Treat all three the same way until a provider publishes Arc-specific contract addresses or endpoint documentation the way Circle has for CCTP and Gateway: as part of the conversation, not part of the confirmed infrastructure.

The directory

Read the status column against a simple test: has the provider published Arc-specific technical detail (a domain ID, contract address, or documented endpoint), or is the connection an inference from a broader partnership, acquisition, or market-commentary mention? Only the first qualifies as testnet-confirmed or better in this category as of 2 Sep 2026 — nothing qualifies as live on mainnet, because Arc mainnet does not exist until 16 September.

Onramps: fiat-to-USDC, a separate question from bridging

Fiat onramps (converting a card or bank payment into USDC that lands on Arc) are a distinct piece of plumbing from cross-chain bridging, and worth naming as its own line. Crossmint has announced a partnership with Arc explicitly covering onramps alongside wallets and checkout infrastructure, though without a published launch date as of 2 Sep 2026.

Builds on Arc: Provides wallet, onramp, checkout and compliance tooling; announced an Arc partnership without a published launch date. · Role: Serves · Category: Developer Infrastructure → Account abstraction

Beyond that, most exchange-side onramps into Arc will likely route through exchanges named as Circle integration partners — Kraken and Upbit among them — rather than through dedicated onramp specialists, though exchange-side Arc deposit/withdrawal support has not been independently verified per-exchange as of this writing. Both hold Role: Integrates (Exchanges & Trading → Exchanges) under v2; they're named here only because Circle's release bundled them alongside bridging and onramp partners, not because either is an onramp specialist — see Built on Arc's exchanges and trading category for their actual filing. For the wallet side of receiving a bridged or on-ramped USDC balance, see Built on Arc's wallet support status guide.

Why native-mint bridging matters more on Arc specifically than on most chains

The distinction between CCTP's native burn-and-mint model and older "lock-and-wrap" bridge designs (where a bridge locks an asset on the source chain and mints a synthetic, wrapped representation on the destination) is not a minor technical footnote on Arc — it's close to the whole point. A wrapped-token bridge introduces a dependency on the bridge contract itself staying solvent and uncompromised; historically, wrapped-bridge exploits have been among the largest categories of losses across the broader industry. Because Arc is built specifically as stablecoin settlement infrastructure, arriving via native mint rather than a wrapped representation is a materially different trust and composability proposition — the USDC that lands on Arc via CCTP is the same asset other Arc-native contracts expect, not a synthetic stand-in that some protocols might not recognize or price correctly. That's a real, structural reason CCTP and Gateway's confirmation status matters more here than a similar confirmation would on a general-purpose chain, and part of why this guide treats them as the clear tier-one confirmed rails in this category.

What changes at mainnet

Everything above is scoped to testnet or to an announced-but-undated integration. At mainnet, the meaningful changes are: CCTP's burn-and-mint model starts moving real-value USDC rather than testnet USDC; Gateway's unified balance becomes a real capital-efficiency tool rather than a testnet demo; and any third-party bridge that wants to claim "live on Arc" will need to publish a mainnet contract address, not just a testnet one or a partnership press release.

Built on Arc is an independent directory. Arc is a Circle product; we are not affiliated with, endorsed by, or operated by Circle.

Sources: - How to: Bridge USDC with CCTP - Arc Docs - Consolidate Crosschain USDC with CCTP and Gateway on Arc - One Integration for Unified USDC Flows with Unified Balance Kit - Circle Signs Agreement to Acquire Interop Labs Team & IP - The Rise of Stablechains: Plasma, Arc, & Tempo Explained (Across) - Crossmint and Circle's Arc Blockchain Forge Partnership - Circle Announces Founding Validator Cohort and Major Integrations for Arc