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 (daily) Methodology

## 1. Overview

Daily Active Users (DAU) for Rocket Pool measures the number of unique user addresses that interact with the liquid staking protocol each day. This metric captures user engagement by counting distinct addresses that either deposit ETH to receive rETH tokens or burn rETH tokens to withdraw ETH. The calculation aggregates user interactions from core Rocket Pool smart contract events on Ethereum.

## 2. Data sources

- **Ethereum blockchain event logs**: Parsed smart contract events from Rocket Pool protocol contracts on Ethereum
- **Rocket Pool contract events**: Specifically `DepositReceived` events from `RocketDepositPool` and `RocketDepositPoolV2` contracts, and `TokensBurned` events from `RocketTokenRETH` contract
- **Event parameters**: User addresses extracted from the `from` parameter of contract events
- **Block metadata**: Block timestamps for temporal aggregation

## 3. Step-by-step calculation

### Component A: User interaction extraction
- **Purpose**: Identify all user interactions with Rocket Pool liquid staking contracts
- **Logic**: Extract user addresses from three types of Ethereum contract events. For `DepositReceived` events from both `RocketDepositPool` and `RocketDepositPoolV2` contracts, the `from` parameter identifies users making deposits. For `TokensBurned` events from the `RocketTokenRETH` contract, the `from` parameter identifies users withdrawing by burning rETH tokens. Each interaction is classified with metadata including chain (ethereum), market sector (liquid_staking), business segment (liquid_staking), and user type (Depositor for deposit events, Withdrawer for token burn events)
- **Key fields**: `block_timestamp` for timing, `transaction_hash` and `log_index` for event identification, `from` parameter as `user_address`, and derived `user_type` classification

### Component B: Daily aggregation
- **Purpose**: Count unique active users per day
- **Logic**: Truncate block timestamps to daily boundaries using day-level granularity. Group all user interactions by the truncated timestamp and apply distinct count to user addresses. This ensures that users who perform multiple interactions within the same day are counted only once. The aggregation maintains chain, user type, and business classification metadata for each daily count
- **Key fields**: `timestamp` truncated to day, `user_address` for distinct counting, `user_type` classification, and business metadata fields

### Final aggregation
- **Combining components**: The user interaction data flows directly into daily aggregation without additional joining or combining steps
- **Currency conversion**: Not applicable for user count metrics
- **Time aggregation**: Daily boundaries are established by truncating block timestamps to day-level granularity, ensuring consistent 24-hour periods
- **Final calculation**: Count distinct user addresses per day across all Rocket Pool liquid staking interactions (deposits and withdrawals), with chain availability filtering applied to ensure data quality and completeness

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

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

Rocket PoolRPL

Active users (daily)

Active users (daily)

Competitive landscape

Chain breakdown