# Hop Protocol

> The cross-chain bridge protocol

Hop Protocol lets users transfer tokens between Ethereum and its Layer 2 networks quickly and at low cost.

Hop Protocol is a cross-chain bridge for moving tokens between Ethereum and its Layer 2 networks without waiting for lengthy withdrawal periods. Users can transfer assets across multiple supported rollups, provide liquidity in AMM pools to earn fees, and integrate bridging into applications via a JavaScript SDK. The protocol relies on Bonders who front liquidity at destination chains, enabling trustless transfers without a central authority.

- Type: Protocol
- Sector: Infrastructure
- Status: Active
- Founded: 2021-01-01
- Profile: https://thegrid.id/profiles/hop_protocol

## Products

- [Hop Protocol](https://thegrid.id/profiles/hop_protocol): Hop Protocol is a rollup-to-rollup token bridge that transfers assets between Ethereum and Layer 2 networks through hToken intermediary tokens and per-chain AMMs. Bonders lock collateral to front liquidity at destination chains, issuing hTokens that users swap for native tokens, with collateral released after a 24-hour on-chain challenge window. The protocol includes a dedicated transfer explorer and a protocol metrics dashboard. (Bridge, Live, Main Product)
- [Hop SDK](https://thegrid.id/profiles/hop_protocol): The Hop JavaScript SDK (@hop-protocol/sdk) provides programmatic access to Hop Protocol bridge functionality, enabling developers to integrate cross-chain token transfers into applications. The SDK handles fee calculation, transaction construction, and AMM interactions across all Hop-supported networks and tokens, with npm distribution and a full API reference. (Developer Tooling, Live, Main Product)
- [Hop Core Messenger](https://thegrid.id/profiles/hop_protocol): Hop Core Messenger is a trustless cross-chain messaging protocol using a hub-and-spoke model where messages are aggregated into bundles whose hashes are relayed between networks via native Ethereum bridges. The architecture targets high-security, non-time-sensitive use cases such as DAO governance and value settlement, and supports collateralized or optimistic messaging layers for time-sensitive applications. (Cross-chain Infrastructure, In Development)

## Assets

- [Hop Protocol Token (HOP)](https://thegrid.id/profiles/hop_protocol): HOP is the governance token of Hop Protocol. It is used to vote on protocol parameters, treasury allocations, and the distribution of liquidity incentives across bridge AMM pools. Holders must delegate voting power before participating in on-chain governance, with off-chain signaling available via Snapshot and binding votes executed through a Governor contract on Ethereum. (Governance)

## Links

- [Main](https://hop.exchange)
- [Documentation](https://docs.hop.exchange)
- [Whitepaper](https://hop.exchange/whitepaper.pdf)
- [Terms of Service](https://hop.exchange/terms)
- [Forum](https://forum.hop.exchange)
- [Governance](https://snapshot.org/#/hop.eth)
- [Governance](https://www.tally.xyz/gov/hop)
- [Twitter / X](https://x.com/HopProtocol)
- [Discord](https://discord.gg/PwCF88emV4)
- [GitHub](https://github.com/hop-protocol)
- [Medium](https://medium.com/hop-protocol)

## Legal

This data is provided under two licensing models.

Model 1 - open data. The open data core is licensed under the Open Database License (ODbL) — a copyleft/share-alike license allowing free use, modification, and sharing for any purpose. Attribution is required: include "Powered by The Grid" linking to https://thegrid.id wherever the data is used. Derivative databases must be shared under ODbL terms. Trademarks, logos, and brand names (marked "Special TPIP") are not covered by the ODbL. For ML/AI use: training datasets that substantially extract ODbL data are Derivative Databases and must be shared under ODbL if publicly used; models must be attributed in documentation.

Model 2 - commercial licenses. The Grid Data Service (TGDS) is also available as a commercial license. See [Web Services Terms](https://about.thegrid.id/legal/web-services-terms) for commercial use that is not covered by the open data service.

The following applies to both licensing models.
- All data is provided AS IS with no guarantees of accuracy.
- The Grid does not provide investment, legal, or tax advice, and
- a project's presence in The Grid's data does not imply endorsement.


- [Data Licensing & Disclaimers](https://about.thegrid.id/legal/data-licensing-and-disclaimers): Licensing models and disclaimers
- [Open Data (ODbL)](https://about.thegrid.id/legal/open-data): Open Database License terms and scope for The Grid's open data service.
- [Attribution Guidelines](https://about.thegrid.id/legal/open-data-attribution-guidelines): How to attribute The Grid's data when using the open data service.
- [Web Services Terms](https://about.thegrid.id/legal/web-services-terms): commercial Terms for using data services.
- [All Legal Documents](https://about.thegrid.id/legal): Full index of terms, policies, and disclosures

## Optional

- [TGS Field Descriptions](https://github.com/The-Grid-Data/workspace-public/blob/main/references/tgs-field-descriptions.md): Schema field definitions for The Grid's data model
- [TGS JSON Structure](https://github.com/The-Grid-Data/workspace-public/blob/main/references/tgs-json-structure.md): Data model structure and relationships
- [Product Type Definitions](https://github.com/The-Grid-Data/workspace-public/blob/main/references/product-type-definitions.md): Definitions for each product type
- [Product Type Classification](https://github.com/The-Grid-Data/workspace-public/blob/main/references/product-type-classification.md): Guide for classifying products into types
- [Grid MCP Guide](https://github.com/The-Grid-Data/workspace-public/blob/main/grid-search/skills/grid-query/references/grid-mcp-guide.md): How to query The Grid programmatically via MCP