Hop allows users to send tokens from one rollup to another almost immediately without having to wait for the rollup’s challenge period. Liquidity providers deposit funds into Hop AMM pools and receive trading fees from traders (supply-side fees).

Hop is a scalable rollup-to-rollup general token bridge. Hop was co-founded by Christopher Whinfrey and launched in 2021.

HOP tokenholders own and govern the protocol. They currently take a cut of the total transfer fees paid by users (revenue). Hop’s investors include 1confirmation, Infinite Capital, etc.

governance

github

twitter

discord

etherscan

website

Bridges

Hop Protocol

# Hop Protocol Active users (daily) Methodology

## 1. Overview

The Hop Protocol Daily Active Users (DAU) metric measures the number of unique addresses that initiate cross-chain bridge transfers through Hop Protocol on any given day. This metric captures user engagement with Hop's bridging infrastructure by counting distinct recipient addresses from transfer events across all supported chains and tokens. The calculation provides insights into daily protocol usage and cross-chain activity patterns.

## 2. Data sources

The DAU calculation relies on these raw data sources:
- **Hop Protocol bridge events**: Parsed `TransferSent` and `TransferSentToL2` events from Hop Protocol's bridge contracts across Ethereum, Arbitrum, Optimism, Polygon, and Base
- **Multi-token coverage**: Bridge events for various tokens including DAI, ETH, USDT, WBTC, HOP, MAGIC, RETH, MATIC, SNX, and SUSD
- **Blockchain transaction data**: Transaction timestamps and hashes from the respective blockchain networks to establish temporal context
- **Event parameters**: Recipient address data extracted from bridge transfer event logs

## 3. Step-by-step calculation

### Component A: Bridge event aggregation
- **Purpose**: Collect all relevant bridge transfer events across the Hop Protocol ecosystem
- **Logic**: The system gathers parsed bridge contract events from five blockchain networks. On Ethereum (L1), it collects `L1Bridge*_TransferSentToL2_event` events for various tokens. On Layer 2 networks (Arbitrum, Optimism, Polygon, Base), it collects `L2Bridge*_TransferSent_event` events. Each event type corresponds to a specific token bridge contract (e.g., DAI bridge, ETH bridge, USDT bridge). The system extracts the `recipient` parameter from each event, which identifies the destination address for the bridge transfer
- **Key fields**: The `recipient` field serves as the user identifier, `block_timestamp` provides temporal context, `transaction_hash` enables event tracking, and chain information identifies the source network

### Component B: User classification and standardization
- **Purpose**: Standardize user data and apply consistent business categorization
- **Logic**: All users identified from bridge events are classified as `Trader` type users, categorized under the `bridges` market sector within the `mint_and_burn` business segment. The recipient address from each transfer event becomes the `user_address`. Each record maintains its source chain identifier and transaction metadata. The system applies a uniform schema across all chains while preserving chain-specific context
- **Key fields**: `user_address` (from recipient parameter), `user_type` (standardized as 'Trader'), `market_sector_id` ('bridges'), `business_segment_id` ('mint_and_burn'), and `chain` identifier

### Final aggregation
- **Combining components**: The system unions all bridge events across chains and tokens into a single user activity dataset, creating a comprehensive view of Hop Protocol usage
- **Time aggregation**: Block timestamps are truncated to daily boundaries using day-level granularity, ensuring consistent daily time buckets regardless of the original transaction timing
- **Deduplication logic**: The calculation applies `DISTINCT` to user addresses within each day, chain, and dimensional combination, ensuring each unique address is counted only once per day even if they performed multiple bridge transfers
- **Final calculation**: The result is a count of unique user addresses per day, representing the daily active users who initiated bridge transfers through Hop Protocol on each supported blockchain network

*This methodology was automatically generated by Token Terminal's methodology analyzer.*

Unique revenue-generating users over a fixed 24-hour window.

Hop ProtocolHOP

Active users (daily)

Active users (daily)

Competitive landscape

Chain breakdown