Stakers deposit funds into Rocket Pool and receive a return on investment in the form of staking rewards (supply-side fees).

Rocket Pool is a non-custodial staking protocol built on Ethereum. Rocket Pool was founded by David Rugendyke and launched in 2021.

RKT token holders own and govern the protocol. They currently take a cut of the total return on investment (revenue).

governance

github

twitter

discord

etherscan

website

Liquid staking

Rocket Pool

# Rocket Pool Active users (monthly) Methodology

## 1. Overview

Monthly Active Users (MAU) measures the number of unique users who interact with Rocket Pool's liquid staking protocol within a rolling 30-day period. This metric provides insight into user engagement and protocol adoption by tracking distinct users who either deposit ETH for liquid staking or withdraw by burning rETH tokens. The calculation uses HyperLogLog data structures for efficient cardinality estimation across large datasets and provides dimensional breakdowns by chain, user type, and product level.

## 2. Data sources

The MAU calculation relies on the following raw blockchain data sources:

- **Ethereum event logs**: Parsed events from Rocket Pool smart contracts including deposit pools and rETH token contracts
- **Smart contract events**: Specific event types including `DepositReceived` events from RocketDepositPool and RocketDepositPoolV2 contracts, and `TokensBurned` events from RocketTokenRETH contracts  
- **Transaction metadata**: Block timestamps, transaction hashes, and log indices for event ordering and daily aggregation
- **User addresses**: Ethereum addresses extracted from event parameters identifying users interacting with the protocol

## 3. Step-by-step calculation

### Component A: User interaction identification
- **Purpose**: Identifies and classifies all user interactions with Rocket Pool contracts
- **Logic**: Extracts user addresses from three specific Rocket Pool contract events on Ethereum. `DepositReceived` events from both RocketDepositPool and RocketDepositPoolV2 contracts identify users making deposits (classified as "Depositor" type). `TokensBurned` events from RocketTokenRETH contracts identify users burning rETH tokens for withdrawals (classified as "Withdrawer" type). Each interaction captures the user address from the `from` parameter, along with transaction metadata including block timestamp, transaction hash, and log index.
- **Key fields**: `user_address` extracted from event parameters, `user_type` classification (Depositor/Withdrawer), `block_timestamp` for temporal analysis, `chain` identifier (Ethereum)

### Component B: Daily active users calculation  
- **Purpose**: Aggregates user interactions into daily distinct user counts while preserving dimensional attributes
- **Logic**: Groups all user interactions by truncated day-level timestamps, taking distinct user addresses per day. Preserves key dimensional attributes including chain, user type, market sector (liquid_staking), business segment, and product ID. This creates the foundation dataset of daily unique users that will be used for the rolling MAU calculation.
- **Key fields**: `timestamp` (day-level), `user_dau` (distinct user addresses), `user_type`, `chain`, `product_id`

### Component C: HyperLogLog initialization and windowing
- **Purpose**: Converts daily user sets into HyperLogLog data structures and creates rolling 30-day windows
- **Logic**: Transforms daily active user data into HyperLogLog sketches for memory-efficient distinct counting across time periods. Creates a complete datespine covering all days in the analysis period to ensure no gaps in the time series. For each day, generates a 30-day rolling window by joining with the previous 29 days, creating sliding windows that capture all user activity within each 30-day period.
- **Key fields**: `hll` (HyperLogLog sketch), `timestamp` (target date), `joinday` (dates within the 30-day window)

### Component D: Dimensional MAU breakdowns
- **Purpose**: Calculates MAU across four different dimensional perspectives
- **Logic**: Aggregates the 30-day windowed data across four distinct dimensional cuts. Project-level MAU merges all HyperLogLog sketches regardless of other dimensions. Chain-level MAU groups by chain identifier (Ethereum). User-type-level MAU separates Depositors from Withdrawers. Product-level MAU groups by product identifier within the liquid staking category. For each dimension, merges HyperLogLog sketches within the 30-day windows and extracts the estimated distinct user count.
- **Key fields**: `dimensions` (breakdown type), `user_mau` (estimated distinct users), dimensional identifiers (`chain_id`, `user_type`, `product_id`)

### Final aggregation
- **Combining components**: Unions all four dimensional breakdowns (project, chain, user type, product) into a single result set with standardized schema
- **Time aggregation**: Uses 30-day rolling windows calculated daily, with each date representing the MAU for the trailing 30-day period ending on that date
- **Data quality**: Applies the finalize metric macro to ensure continuous time series, filling missing days with zeros and applying consistent schema formatting
- **Final calculation**: The MAU value represents the estimated count of distinct users who interacted with Rocket Pool within the 30-day period, calculated using HyperLogLog cardinality estimation for scalable distinct counting across large user sets

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

Unique revenue-generating users over a rolling 30-day window.

Rocket PoolRPL

Active users (monthly)

Active users (monthly)

Competitive landscape

Chain breakdown