Across Protocol

What is Across Protocol?

Across Protocol is an optimistic, intent-based cross-chain interoperability protocol that lets users move assets and execute actions across Ethereum, major Layer 2 networks, and selected non-EVM environments through a relayer-funded settlement model rather than a conventional lock-and-mint bridge. Its core problem is the fragmentation of liquidity and user experience across rollups and appchains: users want an outcome on another chain, while relayers compete to deliver that outcome quickly and are later reimbursed after settlement. Across’s main technical moat has historically been its combination of a single Ethereum-centered liquidity architecture, competitive third-party relayers, no-slippage quote design, and verification through UMA’s optimistic oracle, which allows transfers to be filled quickly while disputes are escalated to UMA’s Data Verification Mechanism rather than to a proprietary validator set.

Across occupies a specialist position in crypto infrastructure rather than the broader role of a Layer 1 settlement network. It is best understood as middleware for DeFi, wallets, aggregators, and chain teams that need cross-chain execution without forcing users to understand bridge routing, canonical withdrawal windows, or native gas requirements. As of mid-September 2026, market data providers placed ACX near the lower end of the top-500 cryptoassets by capitalization, with CoinMarketCap showing a market-cap rank around #498 and DefiLlama showing Across among the larger cross-chain bridge protocols by TVL, with roughly $20 million of bridge TVL and a top-five category position at the time its page was crawled. That TVL figure understates Across’s functional scale because bridge businesses can process large notional flow with limited balance-sheet liquidity; DefiLlama’s bridge dashboard showed Across handling multi-billion-dollar 30-day bridge volume and more than 100,000 daily transactions in mid-September 2026, while official and partner materials have previously cited cumulative usage in the tens of billions of dollars and millions of wallets through integrations such as Jumper Exchange. The more cautious interpretation is that Across has demonstrated meaningful transaction-market fit in bridge routing, but not necessarily durable value accrual to ACX holders.

Who Founded Across Protocol and When?

Across was developed by Risk Labs, the organization associated with UMA, and went live in November 2021, during the first major Ethereum rollup adoption cycle and shortly before the 2022 crypto credit contraction exposed the fragility of many bridge and DeFi balance-sheet models. The initial launch post described Across as a Risk Labs-built bridge secured by UMA’s optimistic oracle and framed its early governance as a “fair fair launch,” with the community intended to shape token distribution and protocol ownership through the eventual Across DAO. Public materials identify Hart Lambur as a key Risk Labs and UMA co-founder associated with Across, while regulatory disclosure documents and exchange risk statements also refer to Risk Labs leadership and core contributors involved in the project’s development; a 2025 Kraken crypto-asset statement described Risk Labs as the primary entity behind the protocol and named Hart Lambur, John Shutt, Matt Rice, and Melissa Quinn in leadership or operating roles for the broader project context (Kraken statement). The ACX token itself launched later, in November 2022, after Across had already operated as a bridge product.

The project’s narrative has shifted materially since inception. In 2021 and 2022, Across was presented primarily as a fast, insured, capital-efficient L2-to-L1 bridge built to demonstrate practical use of UMA’s optimistic oracle; by 2024 and 2025, the emphasis had moved toward intent-based interoperability, developer APIs, embedded cross-chain actions, and the emerging ERC-7683 standard for cross-chain order formats. By 2026, the narrative changed again in a more consequential way: Risk Labs proposed “The Bridge Across,” a transition from a token-governed DAO structure toward a private U.S. C-corporation, arguing that a corporate entity would be better suited for enforceable contracts, institutional partnerships, commercialization, and revenue agreements than a token-based DAO. That proposal subsequently evolved into a formal ACX sunset plan, with Across stating in September 2026 that the protocol had been transferred to Across, Inc. and that ACX would lose governance, utility, and economic function after January 8, 2027 (Across announcement). This is not a cosmetic branding change; it is a fundamental alteration of the token’s investment and governance thesis.

How Does the Across Protocol Network Work?

Across is not a Layer 1 blockchain and does not run its own proof-of-work, proof-of-stake, or delegated validator consensus. It is a cross-chain application and settlement protocol deployed across supported chains, using Ethereum as a central settlement and verification anchor in its historical architecture while relying on the underlying consensus of each connected chain for transaction ordering and finality. In the Across model, a user deposits assets or submits an intent to a SpokePool contract on the origin chain; a relayer observes that intent and fronts liquidity on the destination chain, often within seconds; a dataworker aggregates fills and refund claims into bundles; and those bundles are verified optimistically through UMA before relayers are reimbursed. The security model is therefore closer to optimistic settlement plus bonded dispute resolution than to a standalone validator network. Across documentation explicitly describes the system as requiring at least one honest actor to challenge an invalid bundle during the challenge window, with UMA tokenholders resolving disputes through the DVM if a proposal is contested (security model).

The protocol’s distinct engineering feature is its intent-and-relayer architecture. Instead of asking a user to route through a particular bridge path, Across lets the user specify an outcome, such as receiving a certain token on a destination chain, and lets relayers or solvers handle execution and capital logistics. Its architecture has evolved from same-asset transfers into embedded cross-chain actions and cross-chain swap-plus-execution flows, with APIs that can support wallet signing, gasless execution, and persistent deposit addresses (Across features). Across V4 introduced a more modular expansion model, using Succinct’s SP1 zkVM to generate proofs of Ethereum state so that verified repayment-bundle data can be consumed by other chains through a universal verifier, reducing the need for bespoke chain adapters and audits for every new integration (Across V4). This is technically meaningful, but it does not eliminate bridge risk. Relayer software, off-chain event parsing, chain-specific assumptions, API access controls, and the permissioning around bundle proposal infrastructure remain critical operational dependencies. A July 2026 Solana-side incident, widely reported as involving spoofed deposit-event interpretation by a Risk Labs-operated relayer while user funds were reported safe, illustrated that the attack surface includes off-chain infrastructure and non-EVM integration assumptions, not only audited smart contracts (CryptoTimes report).

What Are the Tokenomics of acx?

ACX was originally designed as the governance and incentive token of Across Protocol, with a capped maximum supply of 1 billion tokens. Early tokenomics allocated tokens across an airdrop, strategic partnerships and fundraising, protocol rewards, and DAO treasury reserves, with Kraken’s 2025 crypto-asset statement summarizing the allocation as 115 million ACX for airdrops, 250 million for strategic partnerships and fundraising, 100 million for protocol rewards, and 535 million for DAO treasury reserves (Kraken statement). As of mid-September 2026, public data providers showed roughly 700 million to 720 million ACX circulating against the 1 billion cap, with the token trading around the $0.04 range and a market capitalization around $30 million depending on the provider and timestamp (DefiLlama token data, CoinMarketCap). Under the original design, ACX was not algorithmically deflationary: there was no structural burn mechanism comparable to an exchange-token buyback-and-burn model, and token supply expansion into circulation was primarily a function of unlocks, rewards, treasury usage, and incentive programs rather than proof-of-stake issuance. The major tokenomics update is now the September 2026 sunset: Across has stated that after January 8, 2027, ACX will be deprecated and will no longer have governance, utility, or economic function.

Historically, ACX value accrual was indirect and weak relative to the protocol’s usage. Users pay bridge-related fees to relayers and liquidity providers; relayers earn compensation for gas, speed, capital lock-up, and execution risk; liquidity providers earn utilization-driven fees for supplying capital; and the DAO previously used ACX emissions to subsidize liquidity and ecosystem participation. That model created network utility, but it did not necessarily route protocol economics to ACX holders. DefiLlama’s token page has shown token-holder net income at zero, reinforcing the point that usage did not automatically translate into cash-flow-like distributions to ACX holders (DefiLlama token data). Earlier governance discussions around the ACX Emissions Committee focused on reducing or managing liquidity-mining emissions over time so that bridge fees, rather than ACX subsidies, could eventually attract liquidity providers (emissions committee proposal). In light of the 2026 corporate transition, however, the prior staking and governance rationale should be treated as legacy. The active economic question for holders shifted from protocol fee capture to whether they could qualify for the equity exchange or accept the USDC buyout terms before the January 8, 2027 deadline described by Across.

Who Is Using Across Protocol?

Across usage is primarily utility-driven bridge and cross-chain execution demand, though that utility is inseparable from speculative crypto-market activity because most cross-chain flows ultimately serve DeFi trading, liquidity migration, farming, arbitrage, or asset rebalancing. The more relevant metric is not spot trading volume in ACX but bridge throughput and integration depth. DefiLlama bridge data in mid-September 2026 showed Across processing large daily and monthly transfer volume relative to its TVL base, while Across’s own and partner-facing materials have cited more than $35 billion of cumulative bridge activity and millions of users or wallets across its operating history. The protocol’s demand base is concentrated in DeFi and wallet infrastructure rather than gaming or real-world assets: users bridge ETH, stablecoins, wrapped BTC, and other ERC-20 assets; aggregators route through Across when quotes are competitive; and applications use Across APIs to abstract away destination-chain gas, swaps, and post-bridge execution.

Institutional or enterprise adoption should be described carefully. Across has notable crypto-native integrations and ecosystem relationships, including work around ERC-7683 with Uniswap-related contributors, participation in the Ethereum ecosystem’s broader intents and interoperability work, and distribution through bridge aggregators such as Jumper. The Ethereum Foundation’s 2025 protocol update described the Open Intents Framework as a collaborative effort involving core contributors from the Ethereum Foundation plus Across, Arbitrum, Hyperlane, LI.FI, OpenZeppelin, Taiko, Wonderland, and others, while also noting that ERC-7683 had been reviewed and revised by contributors from Across, Uniswap, LI.FI, and OpenZeppelin (Ethereum Foundation). These are legitimate infrastructure relationships, but they are not equivalent to bank adoption or regulated-market deployment. The March 2026 corporate-transition proposal explicitly argued that institutional and enterprise work had become harder under the DAO-token structure and that a U.S. corporate entity would improve Across’s ability to sign enforceable agreements and structure revenue arrangements (The Bridge Across proposal). That framing implies both traction and constraint: the product has enough usage to matter, but the tokenized-governance wrapper was viewed by its own backers as a barrier to some commercial relationships.

What Are the Risks and Challenges for Across Protocol?

Across’s regulatory risk is now unusually visible because its own governance history centers on the limits of tokenized ownership. There is no prominent public record, based on current search results, of an active SEC lawsuit specifically naming Across Protocol or ACX, and ACX has appeared in exchange disclosure frameworks such as Kraken’s U.K. crypto-asset statement and LCX’s MiCA-related whitepaper process. However, absence of a named enforcement action is not the same as regulatory certainty. The March 2026 Risk Labs proposal stated that if a token confers equity-like rights, dividends, governance over a corporate entity, or claims on assets, it can become a security under U.S. law and would require an infrastructure of registration, audited financials, and ongoing disclosures that the project did not consider practical for a publicly traded token (forum discussion). The September 2026 sunset therefore reduces one class of future token-governance ambiguity by removing ACX’s post-deadline function, but it creates another set of holder risks around eligibility, KYC, accredited-investor status for U.S. participants, buyout timing, and the treatment of holders who do not act before the deadline.

The technical and market risks are equally material. Across depends on relayer competition, correct off-chain software, UMA oracle dispute incentives, Ethereum settlement assumptions, the operational security of supported chains, and the availability of sufficient liquidity for fast fills. The July 2026 Solana incident demonstrates that even when user funds are reportedly protected, relayers can bear losses and integrations can expose unexpected edge cases in event semantics and data verification. Centralization risk appears not in the form of a classic validator cartel, because Across does not run its own validator set, but in operational dependencies such as Risk Labs-developed software, dataworker behavior, API access, relayer concentration, bundle proposal permissions, and governance or corporate control after the DAO transition. Competitively, Across faces pressure from Stargate, Synapse, Circle CCTP-based routing, native rollup bridges, Hyperlane, deBridge, LayerZero-connected applications, intent networks, wallet-native account-abstraction flows, and eventually more trust-minimized Ethereum interoperability layers. Its economic threat is not simply that another bridge is cheaper; it is that bridge margins can compress toward commodity routing while value accrues to wallets, aggregators, solvers, or canonical asset issuers rather than to the bridge protocol or its legacy token.

What Is the Future Outlook for Across Protocol?

Across’s infrastructure outlook is stronger than ACX’s token outlook, because the protocol continues to address a real market need while the token has been placed on a path toward deprecation. Verified milestones and roadmap themes include the V4 architecture using ZK proofs for scalable chain expansion, broader API-based integration models, support for gasless and embedded cross-chain actions, use of CCTP and other native-settlement primitives where available, and continued participation in ERC-7683 and open-intents standardization. Across documentation in 2026 described support for 24 mainnet chains, Swap API and gasless routes, CCTP V2/CCTPFast support, embedded cross-chain actions, and ZK-proof-based expansion without requiring a governance vote for each new chain (Across features). These are credible infrastructure directions because they map to the industry’s practical problem: users and applications increasingly operate across many chains, but liquidity, identity, gas, and execution remain fragmented.

The structural hurdle is that Across must prove that fast bridge execution can become a durable business rather than a subsidized routing layer. The protocol’s best-case infrastructure thesis rests on becoming embedded in wallets, exchanges, aggregators, and applications as an execution backend for cross-chain actions, while maintaining low loss rates, resilient relayer economics, credible dispute monitoring, and regulatory clarity through Across, Inc. The ACX token, by contrast, should be analyzed as a legacy instrument in wind-down rather than as an open-ended governance asset, given the official statement that it will lose function after January 8, 2027 (ACX sunset announcement). No price prediction is warranted. The relevant forward-looking question is whether Across can retain flow and commercial relevance after separating protocol operations from token governance, and whether its relayer-and-intent model can survive intensifying competition from canonical bridges, native asset issuers, generalized interoperability protocols, and Ethereum-aligned standards that may reduce the need for proprietary bridge liquidity over time.