Crypto Gloss

Across Protocol

Across Protocol is an intent-based cross-chain bridge and swap system supporting blockchain interoperability: users specify the result they want on another network, and relayers can deliver the destination assets before the protocol completes cross-chain settlement. This design can make supported transfers feel fast, but execution time, fees, and available routes depend on the assets, networks, liquidity, and current quote.

What Across Protocol Does

Across lets a user move value between supported blockchains, including routes that swap tokens during the transfer. Instead of asking the user to choose each contract and liquidity hop, the order describes a desired outcome: the source token and amount, destination token and network, recipient, and conditions such as a fill deadline. The app or integration builds the transaction, while relayers compete to fulfill eligible orders.

Across uses SpokePool contracts on supported chains and a HubPool settlement system centered on Ethereum. This is a distinct design from a simple lock-and-mint bridge. The source deposit and destination fill happen on separate chains, and their settlement is coordinated afterward; they are not one atomic transaction.

How a Transfer Works

  1. Deposit: The user submits an order through Across or an integration. The source-chain SpokePool escrows the input and emits a deposit event with the order details.
  2. Fill: A relayer detects the order and, if it chooses to fill it, sends the specified output assets to the recipient on the destination chain using its own capital. Across documentation describes typical fills in seconds, but a quote or interface estimate is not a guarantee.
  3. Settlement: Across’s dataworker matches fills to deposits and groups valid activity into a proposed bundle. The proposal is bonded and subject to an optimistic challenge process. If it is not successfully disputed, settlement can reimburse relayers and coordinate liquidity rebalancing. A disputed proposal can be referred to UMA’s oracle process.

Orders can also have an exclusivity period for a designated relayer. If a fill does not happen before an order’s deadline, the transfer may expire and follow the protocol’s refund process. Check the live deposit status and the terms shown for the exact route rather than assuming every order settles the same way.

Fees and Quotes

The difference between the input and output amounts reflects the quoted transfer cost. Across documents describe liquidity-provider fees and relayer fees; the latter account for factors such as destination-chain gas, capital tied up while settlement completes, and execution risk. Integrators may also add a separate app fee. Fees can vary by token, route, pool utilization, transaction size, and gas conditions, so one route’s quote does not predict another’s.

Before signing, compare the final amount received, network and token addresses, estimated fill time, route limits, and any app fee. Small transfers can be disproportionately affected by fixed gas costs. A fast fill also does not mean that settlement or any later withdrawal is final instantly.

Security and Risks

Across’s design reduces the need for a user to wait for every settlement step before receiving destination assets, but it does not remove bridge risk. A transfer can depend on the source and destination chains, SpokePool and HubPool contracts, relayer software and liquidity, bundle construction, the dispute process, and the tokens being moved. Chain reorganizations, contract bugs, delayed or disputed settlement, thin route liquidity, and mistakes in the recipient or token remain relevant risks.

Across documentation describes bonded, optimistic verification: proposed settlement bundles can be challenged, and UMA’s oracle process can resolve disputes. That mechanism is a security assumption, not a guarantee that losses are impossible. The documentation also describes the dataworker as a designated off-chain actor, so “permissionless relayers” should not be read as “every protocol role is permissionless.” Verify the official app and transaction details, and avoid bridge links sent through unsolicited messages.

Across V4 and ACX: Current Context

Across’s documentation describes V4 as adding a zero-knowledge proof path, using Succinct’s SP1, to communicate finalized Ethereum settlement state to destination-chain contracts. The docs say this changes the settlement layer while the user-facing intent and relayer-fill flow remains similar. Version and route availability can vary, so check the current protocol documentation and the route you are using.

ACX historically served as the Across DAO’s governance token. The official “Bridge Across” documentation now says a proposal to move from a token-based DAO to a private U.S. corporation passed its Snapshot vote and is underway. As checked on 2026-10-19, the same page says the ACX exchange portal is not live and full terms have not yet been shared. That means older descriptions of ACX as an unchanged, active DAO-governance or liquidity-incentive token may be out of date. This status update does not establish ACX’s value or the legal, tax, or financial consequences for any holder. Use only links announced through Across’s official channels.

Social Media Sentiment

In an October 1, 2026 r/defi discussion about how people bridge crypto, some commenters mentioned using Across, while others preferred aggregators or emphasized comparing the route, fees, and final amount. This is one discussion rather than a representative survey, and the comments do not establish which option is best for a particular transfer.

Last updated: 2026-10

Related Terms

See Also

Sources