| Author | Chris Whinfrey |
|---|---|
| Date | January 2021 |
| Project | Hop Protocol |
| Original proposal | Ethereum Research discussion |
This page is an educational summary of a technical proposal, not a verbatim reproduction or investment advice. Crypto Gloss does not claim authorship of the original work.
| Protocol documentation | Documentation |
|---|---|
| Directories | Ethereum Whitepapers & Research |
Hop: Send Tokens Across Rollups is a January 2021 proposal by Chris Whinfrey for moving tokens between Ethereum rollups more quickly than waiting for every transfer to settle through a canonical bridge. Its design combines an intermediary bridge token called an hToken, automated market maker (AMM) pools, and liquidity providers called bonders. This page explains the early proposal and separates it from details that changed in Hop v1.
The transfer-delay problem
Rollups process transactions away from Ethereum mainnet, but users still need ways to move assets between rollups and Layer 1. An exit through an optimistic rollup‘s canonical bridge can require time for invalid state claims to be challenged. In the January 2021 discussion, Whinfrey contrasted Optimism’s then roughly seven-day challenge period with a shorter Hop-specific exit period. Those numbers describe that design context; they are not a universal rule for every rollup or route today.
The proposal aimed to enable quick rollup-to-rollup transfers and faster exits. Cross-rollup contract calls were described as future research, not as a feature users could assume was already implemented.
hTokens and AMM pools
Hop uses hTokens as intermediary bridge assets. Rather than treating each network’s canonical token as interchangeable in every context, the protocol moves a Hop bridge token between rollups and uses a local pool to convert it to the token users expect. Hop’s contracts control hToken minting and burning; the v1 contract documentation describes each hToken as representing a claim on an underlying asset.
AMMs on participating rollups swap between an hToken and that rollup’s canonical token. Their pools help price local liquidity and give arbitrageurs a way to rebalance differences between networks. A pool can become imbalanced: thin liquidity, route demand, fees, and slippage can affect the amount a user receives. A contract-level relationship to an underlying asset does not mean that every pool swap trades at exactly the same market price.
The AMMs are not literally present on every network: Hop’s own FAQ says there is no AMM on Ethereum L1. Users generally interact with the canonical token while the bridge handles the intermediate token.
Bonders and settlement
A bonder fronts liquidity on a destination rollup so a user can receive funds before the slower settlement path finishes. The bonder locks collateral and later relies on transfer proofs and settlement through the bridge contracts to restore its available credit. The service can make a transfer feel faster, but it depends on an available bonder, sufficient liquidity, and a supported route.
It is important to separate two time periods that the older page conflated. In the January 2021 proposal discussion, Whinfrey said Hop’s then-current exit period was one day, compared with Optimism’s roughly seven-day challenge period. The later v1 contract documentation describes transfer roots settling through Layer 1, which could take about a week. These are distinct mechanisms and historical settings, not a guarantee that every Hop transfer takes exactly one day or seven days.
If a bonder is unavailable, a transfer may fall back to the canonical route and take longer. Bonders also tie up capital and take smart-contract, cross-chain settlement, and rollup-security risks. AMMs add liquidity and price risk. Hop changes who bears some of the waiting and liquidity burden; it does not eliminate bridge risk.
From proposal to deployed protocol
Hop’s own v1 FAQ says the protocol went live on mainnet in July 2021, several months after the proposal. The paper is best read as a design document, not a current list of supported chains, assets, fees, or service availability. In January 2026, Authereum Labs announced that it would step back as Hop’s primary development partner and stop driving day-to-day development. That update describes a change in stewardship; by itself, it does not say that every deployed contract stopped operating. Check current official route and contract information before relying on a specific transfer.
Related Terms
See Also
- Across Protocol: Optimistic Cross-Chain Bridge
- Arbitrum: Scalable, Private Smart Contracts
- LayerZero: Trustless Omnichain Interoperability Protocol
Sources
- Chris Whinfrey’s January 2021 proposal and follow-up on Ethereum Research — Provides the original design goals and the author’s explanation of hTokens, AMMs, and the separate Hop and rollup exit periods.
- Hop Protocol v1 contract documentation — Describes the implemented bridge-token model, AMMs, bonder collateral, transfer roots, and settlement path.
- Hop Protocol’s official FAQ — Explains hTokens, bonders, the no-bonder fallback, supported-route context, and the July 2021 mainnet launch date.
- Chris Whinfrey’s Hop introduction on Medium (March 2021) — Summarizes the project’s intended use of hTokens and AMMs between Ethereum scaling networks.
- L2BEAT, “Governance Review #84” (February 3, 2026) — Reports that Authereum Labs would step back as Hop’s primary development partner, stop leading day-to-day development, and support a clean transition. This corroborates the change in development stewardship; it does not say existing Hop contracts stopped operating.