The bridging space has two architectural camps. Lock-and-mint (LayerZero, Wormhole, original Multichain) actually moves messages and mints synthetic representations on the destination chain. Intent-based (Across, Hyperliquid bridge, newer entrants) lets users declare a desired outcome — "I want 100 USDC on Arbitrum" — and lets relayers race to front the funds on the destination chain, settling later via optimistic verification.
Across is the largest production-grade intent-based bridge. After the V4 launch in July 2025, the protocol started routinely posting $1B+ monthly volume, with cumulative volume crossing $22-28B and 15M+ transactions across its history. Q1 2026 daily volume averaged ~$85M, which extrapolates to ~$2.5B/month — roughly 2.5x the immediate post-V4 rate. Average fill time stayed below one minute. The exploit count is still zero, which is the most important metric in bridge land.
I run cross-chain transfers through Across for the L2 ↔ Ethereum legs of my workflow because intent-based fills are predictable in a way that lock-and-mint bridges aren't. Below is the volume decomposition, the relayer economics that make intent-based viable, and where Across structurally loses to LayerZero — there are real gaps, and pretending otherwise distorts the comparison.
The Q1 2026 Volume Math
Across daily volume of ~$85M decomposes by route:
| Route | Daily volume | Share |
|---|---|---|
| Ethereum ↔ Arbitrum | ~$24M | 28% |
| Ethereum ↔ Base | ~$20M | 24% |
| Ethereum ↔ Optimism | ~$15M | 18% |
| L2 ↔ L2 (Arbitrum ↔ Base, etc.) | ~$14M | 16% |
| Other (Polygon, zkSync, Linea, etc.) | ~$12M | 14% |
The L2-anchored concentration tells you what Across is actually optimized for: EVM L2 to/from Ethereum. That's roughly 70% of volume between Ethereum and the three majors (Arbitrum, Base, Optimism). The remaining 30% splits between L2-to-L2 routes and EVM peripheral chains.
For comparison: LayerZero processes ~$1.5-2B daily across 90+ chains. Across does ~$85M daily across maybe 12 chains. Smaller absolute volume, but tighter focus and substantially better UX on the routes it serves.
What V4 Actually Changed
Pre-V4 Across was already an intent-based bridge with optimistic settlement via UMA. V4 (July 2025) added:
- Universal architecture — new chains can be integrated in hours instead of weeks
- ZK proof integration — settlement disputes resolved with cryptographic proofs in addition to the optimistic UMA fallback
- Relayer capacity expansion — broader relayer participation reduces single-relayer concentration on high-flow routes
- Multi-chain fill paths — relayers can bridge through intermediate chains when direct liquidity is shallow
Volume went from ~$400-600M monthly pre-V4 to $1B+ monthly post-V4 within roughly four months. The growth is real but should be contextualized — bridge volume is heavily reflexive with broader L2 activity. Q3-Q4 2025 saw L2 transaction count grow ~40% across the major L2s, so part of Across's volume growth is just riding L2 ecosystem expansion.
Why Intent-Based Wins on UX
The UX differential is concrete. On a lock-and-mint bridge:
- User initiates transfer on source chain
- Source chain transaction confirms (variable, 1-15 min depending on chain)
- Bridge oracle/messenger relays event to destination chain (1-30 min depending on bridge)
- Destination chain mints/releases assets (additional confirmation time)
Total latency: typically 5-30 minutes, sometimes hours when networks congest.
On Across:
- User signs intent on source chain
- Relayer fronts assets on destination chain immediately (sub-1-minute typical)
- Optimistic settlement reconciles relayer reimbursement asynchronously (user doesn't wait)
Total user-perceived latency: under 1 minute for ~80% of transactions.
That speed differential matters most for arbitrage and active trading workflows. For long-tail "send funds and forget" operations, latency matters less. So Across's structural fit is liquid trading flow, not retail one-off transfers.
The Relayer Economics
Across operates through relayers — entities that front capital on destination chains and get reimbursed via optimistic settlement. Q1 2026 relayer landscape:
- Active relayers: ~25-50 entities
- Top 10 relayer concentration: ~60-75% of fill volume
- Relayer fee per transaction: ~0.05-0.20% of value
- Estimated annualized relayer revenue: ~$25-65M combined
Top-end relayer concentration is the structural bottleneck. Operating a competitive relayer requires:
- Capital deployed across destination chains (typically $10-50M minimum for serious operators)
- Inventory management infrastructure rebalancing capital across chains
- MEV-aware fill prioritization (winning intent auctions requires speed)
- Operational reliability (failed fills cost money)
This favors sophisticated market makers and discourages amateur participation. The 60-75% top-10 concentration isn't going to materially decentralize. That's a structural feature, not a bug — but worth understanding for users evaluating the protocol's decentralization claims.
ACX Token Allocation
ACX token Q1 2026 metrics:
- Market cap: ~$0.18-0.32B (variable across the quarter)
- Allocation: 52.5% DAO Treasury Reserve, 25% strategic partnerships, 12.5% airdrops, 10% protocol rewards
- Utility: governance, relayer reward programs, fee discounts for high-volume users, staking rewards from protocol fees
The 52.5% DAO Treasury concentration is notable — most token supply isn't yet circulating. Continued unlocks across 2026-2027 create supply pressure on price independent of protocol fundamentals. ACX is a bet on Across protocol economics outpacing supply emission, which is a different bet than just "Across is good."
I don't hold ACX. The protocol works well for me as a user; that's separate from whether the token is appropriately priced.
Where Across Loses to LayerZero
Three structural gaps:
Chain breadth. LayerZero supports 90+ chains including Solana, TON, Aptos, Sui, Cosmos chains, and many EVM peripherals. Across supports ~12 EVM chains. For multichain operations across the long tail (Bitcoin L2s, alternative L1s, niche chains), Across isn't even an option.
Protocol integration depth. LayerZero is integrated into substantially more DeFi protocols at the contract level. When a protocol wants cross-chain messaging primitives (governance, token standards, oracle data), LayerZero is the default choice. Across is purpose-built for value transfer, not generic messaging.
Non-EVM coverage. Solana represents meaningful cross-chain demand and Across has zero native Solana support. For Solana ↔ EVM flows, users have to use Wormhole, deBridge, or alternatives.
These aren't fixable through marketing or token design — they're architectural. Across has chosen depth over breadth on EVM L2 routes and that choice has costs.
My Allocation
For my own cross-chain operations (~$50-150K monthly transfer volume across various trading workflows):
- Across: ~30-40% of cross-chain volume, focused on L2 ↔ Ethereum and L2 ↔ L2 EVM routes
- Direct rollup native bridges (Arbitrum bridge, Optimism bridge): ~25-35% for one-way withdrawals where time isn't critical
- Stargate (LayerZero stablecoin pool): ~15-20% for stablecoin-specific operations
- Wormhole/deBridge: ~10-15% for Solana ↔ EVM flows
- Other: ~5-10% for niche routes
Across captures the bulk of my active EVM cross-chain operations specifically because the speed and predictability matter for trading workflows. For batch operations or one-off transfers, native rollup bridges or Stargate work fine and sometimes have better fees.
Decision Framework
For active EVM L2 trading flows: Across is the right default. Predictable sub-1-minute fills outweigh marginal fee differences.
For one-way withdrawals back to Ethereum mainnet (no urgency): Native rollup bridges. Free settlement (just gas), minor wait (7 days for Optimistic rollup withdrawals or near-instant for ZK rollups).
For stablecoin-specific cross-chain: Stargate or Circle CCTP have very tight USDC routing. Worth comparing per route.
For Solana ↔ EVM: Wormhole or deBridge. Across doesn't serve this route.
For long-tail multichain (Cosmos, alternative L1s): LayerZero-based bridges (Stargate) or chain-specific solutions.
For governance/messaging cross-chain: LayerZero or Hyperlane. Across is value transfer only.
What I Watch For
Volume sustainability above $1B monthly. If Across holds $1B+ monthly through 2026, intent-based architecture has clearly captured a structural share of EVM cross-chain flow. If volume slips back below $700M, V4 was a temporary boost rather than a step change.
Relayer concentration trajectory. If top-10 relayer share grows above 80%, decentralization concerns become harder to dismiss. If it drops below 50%, the architecture is genuinely decentralizing.
Non-EVM expansion. Across has discussed Solana support. Actual deployment would be a meaningful expansion. Lack of expansion through 2026 confirms the EVM-only structural positioning.
Bridge exploit landscape. Across has zero exploits across $28B+ cumulative volume — that's a significant track record. A meaningful exploit would compress positioning fast. So far the optimistic settlement design has held up.
Intent-based competition. Other protocols are building intent-based architectures. If a competitor captures meaningful share, Across loses its UX moat. So far no competitor has matched the V4 implementation in production.
Caveats
The volume, decomposition, and relayer-economics figures are from Across's official dashboards, on-chain analytics, and DeFi Llama through April 2026. Daily volume is approximated — exact figures fluctuate ±20% across the quarter and depend on whether L2-to-L2 multi-hop fills are counted as one transaction or multiple. The relayer economics are estimated; Across does not publish per-relayer revenue. The ACX market cap reflects fully-diluted estimates and circulating supply differs based on unlock schedule. The competitive comparison with LayerZero uses publicly disclosed LayerZero metrics and may not be apples-to-apples on all volume measures. Personal positioning observations reflect my own usage patterns and aren't recommended allocations. Bridge security risk, smart contract risk, and relayer counterparty risk apply — size positions accordingly.