Across Protocol: Optimistic Cross-Chain Bridge

Authors No individual author identified in the linked documentation
Publication No dated standalone whitepaper identified
Project Across Protocol
License Not stated for a standalone whitepaper
Official Source Across Protocol: Intent Architecture

This page is an educational summary of official protocol documentation and version history. It is not a verbatim reproduction or a summary of a verified, dated whitepaper. CryptoGloss does not claim authorship of the linked material.

Directories Ethereum Whitepapers & Research

Across is a cross-chain transfer protocol that has evolved from a pooled-liquidity bridge into an intent-based system with several settlement versions. The official material linked here is living protocol documentation, not a dated standalone 2021 whitepaper. This overview therefore separates the design history from current V3/V4 descriptions instead of presenting every feature as one unchanging system.

How an Across transfer is organized

In an intent-based transfer, a user specifies the desired result, such as moving a supported asset from one chain to another. A relayer can front liquidity on the destination chain and fill the request before it has been reimbursed. Across documentation describes three broad layers: the request-for-quote mechanism, the competing relayer network, and settlement. The user-facing transfer and the later repayment are separate steps, so fast delivery does not mean that cross-chain settlement has already finished.

Across’s V3 documentation describes a HubPool on Ethereum and SpokePools on supported chains. Liquidity providers supply capital; relayers use their own capital to fill transfers; and a dataworker groups fills into repayment bundles. After verification and settlement, relayers are reimbursed and liquidity is rebalanced. Timing, supported assets, route availability, and costs depend on the route and live conditions.

Optimistic verification and UMA

Across proposes repayment bundles with a bond and an opportunity for someone to challenge an invalid bundle during the applicable challenge window. The UMA Optimistic Oracle is part of this economic verification process. This is not the same as saying every transfer has immediate cryptographic finality: a relayer may fill a user’s request quickly, while bundle review, settlement, and reimbursement happen later. The relevant timing and contract behavior depend on the version and route; a fixed dispute period should not be assumed.

What V4 changes

Across announced V4 in July 2025. The current documentation describes V4 as a change to the settlement layer: it adds zero-knowledge proofs of Ethereum state to help verify finalized settlement messages on destination chains. The repayment bundle is still proposed and checked through Across’s optimistic process before its state is used for the proof. V4 does not make the entire system a single proof, remove the relayer role, or erase all chain-specific and operational risks.

Across’s versioned documentation is the best place to check what is active for a particular route. Feature descriptions, supported networks, tokens, and settlement implementations can change; the project’s launch announcement should be read as the project’s account of the release, not as an independent audit.

Fees and liquidity

A transfer’s total cost can include a relayer fee, liquidity-provider fee, gas, and other route-specific costs. Relayers front capital and bear operational and price risks while waiting for repayment; liquidity providers supply capital to the system and may receive fees. These roles explain the protocol’s capital model, but they do not guarantee that every route is cheaper than another bridge or that a quoted rate will remain available.

Risks and limits

Cross-chain transfers involve more than one contract and network. Relevant risks can include smart-contract defects, incorrect or delayed messages, oracle or dispute failures, relayer or liquidity shortages, token-mapping mistakes, chain congestion, and user errors such as selecting the wrong asset or destination. An optimistic challenge process and ZK proofs address specific parts of settlement; neither removes every risk. Check the route, asset, destination, fees, and current contract documentation before signing a transaction.

Social Media Sentiment

A small r/defi discussion about cross-chain bridge usability included concerns about confusing route choices, approvals, and the risk of a mistaken transfer. The thread discussed bridges generally, not Across specifically, and has limited engagement; it is a narrow snapshot of user concerns rather than a measure of sentiment about this protocol.

Last updated: 2026-10

Related Terms

  • Cross-Chain Bridge Security — Security assumptions and common risks in systems that move value between chains.
  • Optimistic Rollup — A Layer 2 design that accepts proposed state updates unless challenged under its rules.
  • Liquidity Pool — A shared pool of assets used to support swaps, lending, or other on-chain activity.

See Also

Research