Across Protocol and Arc: named in commentary, not confirmed as a bridge

Across Protocol has published its own commentary discussing Arc as part of the broader "stablechain" landscape, alongside Tempo and Plasma — a genuine, sourced mention, but market commentary, not a deployment announcement. As of 2 September 2026, no Arc-specific deployed bridge integration, contract address, or technical documentation for Across was found. Across does not appear in Circle's 5 August 2026 founding-validator-and-integrations release.

Builds on Arc: Bridge protocol that writes about Arc's market but has no confirmed route for moving assets there. · Role: Serves · Category: Bridges & Onramps → Interop messaging · Project page

What Across actually is

Across Protocol is a cross-chain bridge focused primarily on fast, capital-efficient transfers, historically centered on moving assets between Ethereum and its Layer-2 rollups, and more recently promoting large-USDC-transfer capability more broadly. It is an established, actively used bridge in the general Ethereum-ecosystem sense — the question this page answers is narrower: whether that bridge specifically connects to Arc.

What the Across blog post actually says, and doesn't

Across published "The Rise of Stablechains: Plasma, Arc, & Tempo Explained" on its own blog — market analysis discussing Arc as one of several purpose-built stablecoin chains entering the landscape, alongside Tempo (Stripe/Paradigm-backed, mainnet 18 March 2026) and Plasma. This is a real, dated, sourced piece of content, and it is worth citing accurately for what it is: commentary and industry positioning, written from the outside looking in at a category Across itself operates adjacent to. It is not a statement that Across has deployed bridge infrastructure to Arc, published a contract address for Arc, or listed Arc among its supported chains. Separately, Across promotes general large-USDC-bridge capability in its own marketing, but that is a general product capability claim, not an Arc-specific one.

Relationship to Arc, as of 2 Sep 2026

Why a company writing about a chain isn't the same as supporting it

This is a distinct trap from the Axelar-acquisition case elsewhere in this cluster, but a related one: any company actively building infrastructure has an incentive to publish informed commentary about a major new entrant in its own competitive category, whether or not it has anything shipped there. Across writing thoughtfully about Arc's design and market position is exactly what you'd expect from a serious bridge provider paying attention to its own industry — and it says nothing, on its own, about whether Across has done, or plans to do, the technical work of deploying to Arc.

Where the confirmed bridging rails on Arc actually are

Circle's own CCTP is documented directly by Arc's developer docs, with a dedicated CCTP domain (domain 26) and a native burn-and-mint transfer model — no wrapped or synthetic token representation. Circle Gateway is separately documented for consolidating cross-chain USDC into a unified balance accessible on Arc. Both are Circle-built, Circle-documented, and materially ahead of any third-party bridge's confirmation status for Arc, Across included. See Built on Arc's bridges and onramps status guide for the full comparison, including Axelar and LayerZero, which sit in a similarly unconfirmed position.

Where the how-to lives

This is a status page, not a walkthrough. For step-by-step instructions on bridging USDC to Arc, see Meme Central's bridging guide — how-tos are their lane, not this directory's.

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

Sources: - The Rise of Stablechains: Plasma, Arc, & Tempo Explained — Across - How to: Bridge USDC with CCTP — Arc Docs - Circle Announces Founding Validator Cohort and Major Integrations for Arc