ChainPick

Across Protocol vs Hop Protocol (2026)

A head-to-head comparison of Across Protocol and Hop Protocol — pricing, the features that actually differ, and which one fits which use case.

At a glance

A

Across Protocol

Intent-based cross-chain bridge with the fastest settlement and lowest fees on EVM routes

4.6(1,240)
Starting price
Free
Free plan
Yes
Best for
Fastest EVM bridge — ~2 minutes vs hours for canonical bridges
Full Across Protocol review →
H

Hop Protocol

Specialized bridge for fast Ethereum L2-to-L2 transfers

4.3(142)
Starting price
Free
Free plan
Yes
Best for
Near-instant L2-to-L2 transfers
Full Hop Protocol review →

Where Across Protocol and Hop Protocol differ

These are the 5 capabilities where the two tools genuinely diverge — the rest of their feature sets overlap.

CapabilityAcross ProtocolHop Protocol
Settlement Time~2 minutes~1-5 min
Bridge ModelIntent-based (relayer network)Bonded liquidity (hTokens)
Fee ModelDynamic LP fee onlyBonder fee
Canonical SecurityYesNo
Cross Chain MessagesYesNo

Full feature comparison

FeatureAcross ProtocolHop Protocol
Settlement Time~2 minutes~1-5 min
Bridge ModelIntent-based (relayer network)Bonded liquidity (hTokens)
Fee ModelDynamic LP fee onlyBonder fee
Canonical Security
Cross Chain Messages
Governance Token
Multi Chain
Self Custody
Arbitrary Messaging
Non Evm Support

Pricing compared

Both tools are free to use — costs come from network or usage fees.

Across Protocol

Across Protocol

Free (LP fee only)

Free

  • 12+ EVM chains
  • ~2 minute settlement
  • 0.05–0.15% LP fee
  • USDC, ETH, WBTC, DAI, USDT
  • No protocol fee
Get Started

Hop Protocol

Hop Protocol

Free (bridge fee only)

Free

  • Fast L2-to-L2 transfers
  • Bypasses native withdrawal delays
  • ETH + stablecoins + more
  • Arbitrum/Optimism/Base/Polygon
  • HOP governance token
Get Started

Which should you choose?

Choose Across Protocol if…

  • Fastest EVM bridge — ~2 minutes vs hours for canonical bridges
  • Consistently lowest fees for stablecoin transfers across major EVM routes
  • Canonical bridge security inherited — relayers are reimbursed through canonical bridges

Watch out: EVM-only — no Solana, Bitcoin, or non-EVM chain support.

Choose Hop Protocol if…

  • Near-instant L2-to-L2 transfers
  • Bypasses days-long native withdrawal periods
  • Purpose-built for the multi-rollup ecosystem

Watch out: Curated asset/chain set, not universal.

Our verdict

Across Protocol edges ahead on our editorial score (4.6/5), but these tools aren’t straight substitutes. Pick Across Protocol when fastest evm bridge — ~2 minutes vs hours for canonical bridges matters most to your workflow; pick Hop Protocol when near-instant l2-to-l2 transfers is the priority. The deciding factor is usually the trade-off you can least afford — Across Protocol means accepting that evm-only — no solana, bitcoin, or non-evm chain support, while Hop Protocol means curated asset/chain set, not universal.

Frequently asked questions

Is Across Protocol or Hop Protocol better?

Across Protocol carries the higher editorial rating (4.6/5 vs 4.3/5), but they solve different problems. Across Protocol is the stronger pick when you need fastest evm bridge — ~2 minutes vs hours for canonical bridges. Hop Protocol wins when near-instant l2-to-l2 transfers.

Which is cheaper, Across Protocol or Hop Protocol?

Both tools are free to use, with costs coming from network or usage fees rather than subscriptions.

What are the main drawbacks of Across Protocol and Hop Protocol?

Across Protocol's main limitation is that evm-only — no solana, bitcoin, or non-evm chain support. For Hop Protocol, curated asset/chain set, not universal. Weigh these against how you actually plan to use the tool.

Can you use Across Protocol and Hop Protocol together?

In most cases yes — many teams run both, using each where it's strongest. Since Across Protocol leads on fastest evm bridge — ~2 minutes vs hours for canonical bridges and Hop Protocol on near-instant l2-to-l2 transfers, the two are often complementary rather than mutually exclusive.