A data-driven comparison of Hop Protocol and Across Protocol, two leading canonical bridge alternatives for EVM-native asset transfers.
Hop Protocol excels at optimistic rollup-to-rollup transfers because its architecture uses a network of automated market makers (AMMs) on each destination chain. This creates a deep, permissionless liquidity pool for assets like USDC, ETH, and DAI, enabling fast, low-cost swaps between L2s like Arbitrum, Optimism, and Polygon. For example, a user can bridge from Arbitrum to Optimism in ~5-10 minutes with fees often under $1, leveraging bonded relayers and a fraud-proof system for security.
Across Protocol takes a different approach by utilizing a single, unified liquidity pool on Ethereum mainnet and a network of off-chain relayers. This model results in a key trade-off: it often provides lower fees and faster finality for mainnet-centric transfers (often 1-3 minutes) because the relayers compete to fulfill transfers instantly, but it can be less capital-efficient for direct L2-to-L2 routes that don't involve mainnet as a hub. Its security relies on the UMA Optimistic Oracle for dispute resolution.
The key trade-off: If your priority is frequent, low-cost swaps between various L2s and sidechains, choose Hop. Its AMM model is purpose-built for that mesh network. If you prioritize the fastest, cheapest route to or from Ethereum mainnet, especially for large institutional transfers, choose Across. Its single-sided liquidity and relayer competition optimize for that specific flow.
Key architectural and economic trade-offs at a glance. Hop prioritizes composability and speed, while Across focuses on capital efficiency and security.
Optimistic rollup model: Uses canonical bridges for finality, then provides instant liquidity via bonded relayers. This enables sub-1 minute transfers for major assets like ETH, USDC, and DAI. This matters for high-frequency trading, arbitrage, and user experience where waiting for 7-day withdrawal periods is unacceptable.
Modular design: The Hop Protocol (AMM) and Hop Exchange (frontend) are separate. Developers can integrate the bridge directly into dApps using SDKs. This matters for DeFi protocols, cross-chain aggregators, and wallets needing seamless, programmable bridging logic without redirecting users.
Single-sided liquidity pools: Uses a unified pool (like USDC) on the destination chain, with a dynamic fee model to rebalance via arbitrage. This reduces capital lockup by ~80% compared to traditional lock-and-mint models. This matters for liquidity providers and DAOs seeking higher yield on deployed capital and lower fees for users.
UMA's Optimistic Oracle: Disputes are settled by a decentralized oracle network, not a multisig. This creates a ~2-hour challenge period for fraud proofs instead of relying solely on trusted relayers. This matters for institutional users and high-value transfers where minimizing custodial risk is the top priority.
Direct comparison of key bridging metrics and mechanisms for EVM chains.
| Metric | Hop Protocol | Across Protocol |
|---|---|---|
Primary Mechanism | Liquidity Network + Bonders | Optimistic Oracle + Relayers |
Avg. Bridge Time (Ethereum L1) | ~15-30 minutes | ~3-5 minutes |
Supported Chains | Ethereum, Arbitrum, Optimism, Polygon, Gnosis | Ethereum, Arbitrum, Optimism, Polygon, Base |
Native Gas Fee Coverage | ||
Avg. Bridge Fee (Ethereum → Arbitrum) | ~0.05% - 0.1% | ~0.05% - 0.08% |
Capital Efficiency Model | Locked Liquidity per chain | Single-Sided Liquidity Pool (UMA) |
Governance Token | HOP | ACX |
Direct comparison of key metrics and features for cross-chain bridging between EVM chains.
| Metric | Hop Protocol | Across Protocol |
|---|---|---|
Primary Security Model | Optimistic Verification | UMA Optimistic Oracle |
Avg. Bridge Time (Ethereum L1) | ~15-30 min | ~3-8 min |
Avg. Total Cost (Ethereum L1) | $10-30 | $5-15 |
Supported EVM Chains | 8+ | 10+ |
Native Gas Refund | ||
Capital Efficiency | Lock & Mint | Bonded Liquidity Pools |
Total Value Secured | $200M+ | $500M+ |
Key strengths and trade-offs at a glance for two leading canonical bridges.
Optimistic Rollup-native design: Uses canonical bridges on L2s (Arbitrum, Optimism) for finality, then AMMs for liquidity. This enables sub-5 minute transfers for major assets like ETH, USDC, and DAI. Ideal for users prioritizing speed and direct withdrawals to their L2 of choice without intermediate wrapping.
Bonder network provides instant liquidity: Users receive funds immediately on the destination chain, with bonders assuming the withdrawal delay risk. This creates a seamless UX comparable to a CEX. The system is highly efficient for high-volume corridors supported by professional market makers.
Optimistic Oracle-enabled validation: Relies on UMA's oracle for attestations, skipping expensive on-chain proofs. This results in consistently lower fees, often 20-50% cheaper than alternatives for large transfers. The trade-off is a longer wait time (20-30 min) for the challenge period. Best for cost-sensitive, non-time-sensitive moves.
Centralized liquidity pool (WETH/USDC) with relayers: Uses a single pool on Ethereum, with relayers filling orders on destination chains. This model concentrates liquidity, reducing fragmentation and slippage for large transfers. It excels at moving value (ETH, WETH, USDC) rather than a wide array of tokens.
AMM liquidity is fragmented per chain: Requires liquidity pools on every supported chain (Arbitrum, Polygon, etc.). This can lead to higher slippage on newer or less-liquid routes. The system is also more complex, relying on the health of both the canonical bridge and the bonder network.
Speed limited by oracle challenge period: The 20-30 minute delay is a fundamental design constraint, making it unsuitable for arbitrage or urgent transactions. The model also introduces relayer dependency, creating potential centralization points compared to Hop's permissionless bonder model.
Key strengths and trade-offs for EVM-native bridging at a glance.
Optimistic model with bonded relayers: Uses a single liquidity pool per chain (e.g., USDC on Ethereum) and a network of bonded relayers to fulfill transfers. This means ~4-10x higher capital efficiency than lock-and-mint models. This matters for protocols with large, frequent cross-chain transfers where idle liquidity is costly.
Fast, single-transaction user experience: Transfers are typically completed in minutes, as they only require confirmation on the destination chain after a relayer commits funds. This matters for users and dApps (like perpetual DEXs or NFT bridges) that prioritize speed over absolute lowest cost and can accept the security model of bonded relayers.
Verdict: The established, capital-efficient choice for high-frequency, multi-chain operations. Strengths:
Verdict: The optimal bridge for single, large-value transfers with a focus on speed and cost predictability. Strengths:
A data-driven breakdown of the core trade-offs between Hop and Across to guide your bridge selection.
Hop Protocol excels at multi-chain liquidity and composability because of its canonical token bridging model and network of automated market makers (AMMs). This architecture, which uses hTokens and a bonder network, provides deep liquidity for major assets like ETH, USDC, and DAI across chains like Arbitrum, Optimism, and Polygon. For example, its TVL often exceeds $50M, enabling large transfers with minimal slippage. Its modular design also makes it a preferred integration for aggregators and dApps seeking a unified bridge interface.
Across Protocol takes a different approach by prioritizing cost-efficiency and speed for specific routes through a single, optimized liquidity pool on Ethereum and a network of off-chain relayers. This results in a trade-off: while potentially offering lower fees and faster times for high-volume routes (e.g., Arbitrum to Ethereum), its liquidity is concentrated, making it less ideal for newer or lower-volume chains. Its reliance on UMA's optimistic oracle for security provides a unique, capital-efficient security model distinct from Hop's bonded validator set.
The key trade-off is between generalized liquidity versus optimized cost/speed. If your priority is supporting users across a wide array of EVM chains with consistent, composable asset flows, choose Hop. It's the superior choice for dApps like decentralized exchanges (e.g., Uniswap) or wallets that require a one-stop bridge for multiple assets and destinations. If you prioritize the absolute lowest cost and fastest finality for high-volume transfers between major networks like Arbitrum-Ethereum, and can accept a more focused chain support, choose Across. It's often the backend for leading bridge aggregators like Socket and Li.Fi for these specific routes.
Stop patching. Start engineering. Get a free technical roadmap and a 30min strategy call.