How Does Hop Protocol Work?
A cross-chain bridge that moves tokens between Ethereum and Layer 2 networks like Optimism and Arbitrum using specialized intermediaries called bonders. It holds $50M across multiple chains. Its B grade reflects a trust-minimized design where bonders cannot steal funds but can cause delays.
TVL
$4M
Sector
Bridge
Risk Grade
B
Value Grade
C-
Core Mechanisms
Bridge/Rollup-Native
Rollup-native bridging using hTokens as intermediate transfer assets
Hop uses specialized bridge tokens (hTokens) that are minted on L1 and burned/minted across L2s, enabling fast cross-rollup transfers without relying on external validators or multisigs.
Bridge/Bonder
Bonder-fronted liquidity for instant cross-chain settlement
Bonders front liquidity on destination chains by verifying rollup state, then reclaim funds after canonical withdrawal completes. Novel trust model where bonders cannot steal funds but can cause delays.
AMM/Stable-Swap
Per-chain AMMs for hToken-to-canonical-token swaps
Each supported L2 has an AMM pool enabling swaps between hTokens and canonical tokens. Low impermanent loss due to same-asset pairing.
Staking/Collateral
HOP token staking for bonder collateral
Bonders must stake HOP tokens as collateral to participate, with stake reduced during active transfers and restored upon settlement.
Governance/Token
HOP governance token with DAO treasury control
Standard governance token model with 1B total supply. DAO manages protocol parameters and treasury.
Fee/Dynamic
Dynamic fee structure based on bonder risk and AMM slippage
Fees combine bonder fees (for fronting liquidity) and AMM swap fees, varying by route and liquidity depth.
How the Pieces Interact
Bridge security is only as strong as the weakest supported rollup. A vulnerability in any single rollup could compromise bonder funds and delay settlements across the entire protocol.
If AMM liquidity dries up on a particular L2, hTokens cannot be efficiently swapped to canonical tokens, creating a de facto depeg and trapping user funds in illiquid positions.
Bonder capital is locked during active transfers; during high-volume periods, insufficient bonder liquidity forces users through slower canonical withdrawal paths.
Initial bonder whitelisting creates centralization risk. If whitelisted bonders collude or go offline simultaneously, the protocol degrades to slow canonical bridge speeds.
What Could Go Wrong
- Bonder liveness dependency — offline bonders delay transfers to rollup exit times
- Bridge security limited by weakest supported rollup chain
- AMM liquidity fragmentation across multiple L2 deployments
Rollup Compromise Bonder Fund Drain
ModerateTrigger: A supported rollup (e.g., Optimism, Arbitrum, or a newer L2) experiences a sequencer exploit or bridge vulnerability enabling fraudulent state transitions
- 1.Rollup vulnerability allows forging withdrawal proofs or state roots — Bonders verify fraudulent state and front liquidity on destination chains
- 2.Bonders advance funds to destination based on manipulated rollup state — Canonical withdrawal never completes, bonders absorb total loss of fronted liquidity
- 3.Remaining bonders reduce exposure by pausing or exiting affected routes — Cross-chain transfer speeds degrade to canonical withdrawal times (7+ days)
- 4.Users unable to quickly exit positions on affected L2 — hToken liquidity on affected chain dries up as LPs withdraw from AMMs
- 5.hTokens depeg on affected chain with no efficient path to canonical tokens — Users holding hTokens face 10-50% haircut or indefinite lock-up
Risk Profile at a Glance
Overall: B (23/100)
Lower score = safer