Stakers deposit funds into StakeStone and receive a return on investment in the form of staking rewards (supply-side fees). StakeStone then deploys the staked capital to Lido.

StakeStone is an omni-chain LST (Liquid Staking Token) protocol aiming to bring native staking yields and liquidity to Layer 2s. StakeStone was founded by a anonymous team and launched in 2023.

StakeStone team controls the protocol. They do not currently take a cut of the total staking rewards earned by the protocol (revenue).

github

twitter

discord

website

Liquid staking

StakeStone

# StakeStone Active users (daily) Methodology

## 1. Overview

Daily Active Users (DAU) for StakeStone measures the number of unique wallet addresses that interact with StakeStone's liquid staking protocol each day. This metric tracks user engagement by counting distinct addresses that either deposit ETH into the StoneVault contract or withdraw assets from the AssetVault contract on Ethereum. The metric provides insight into daily protocol adoption and user activity patterns for StakeStone's liquid staking service.

## 2. Data sources

The calculation relies on the following Ethereum blockchain data sources:
- **StakeStone function calls**: Parsed Ethereum transaction traces for `withdraw` function calls on StakeStone's AssetVault contract, capturing withdrawal operations where users retrieve staked assets
- **StakeStone event logs**: Parsed Ethereum event logs for `Deposit` events emitted by StakeStone's StoneVault contract, capturing deposit operations where users stake ETH
- **Transaction status data**: Ethereum transaction execution status to validate successful operations and filter out failed transactions

## 3. Step-by-step calculation

### Component A: User interaction extraction
- **Purpose**: Identifies all user addresses that interact with StakeStone's liquid staking contracts through deposits and withdrawals
- **Logic**: Extracts user addresses from two distinct interaction types on Ethereum. For withdrawal operations, parses the `withdraw` function calls on the AssetVault contract and captures the `_to` parameter as the recipient address. For deposit operations, parses `Deposit` events from the StoneVault contract and captures the `account` parameter as the depositor address. Only includes successful withdrawal transactions by filtering on transaction status, while deposit events are included regardless of transaction status as events are only emitted on successful execution.
- **Key fields**: `user_address` (extracted from `_to` parameter for withdrawals or `account` parameter for deposits), `user_type` (classified as either "Withdrawer" or "Depositor"), `block_timestamp` (transaction execution time), `transaction_hash` (unique transaction identifier), and protocol metadata fields

### Component B: User classification and metadata assignment
- **Purpose**: Standardizes user interactions with consistent protocol classification and business context
- **Logic**: Assigns each user interaction to the liquid staking market sector and business segment, with stakestonev1 as the product identifier. Classifies users by interaction type as either "Depositor" for users staking ETH or "Withdrawer" for users retrieving staked assets. Maintains chain identification as Ethereum and preserves transaction-level details including block timestamp and transaction hash for temporal analysis.
- **Key fields**: `market_sector_id` (set to "liquid_staking"), `business_segment_id` (set to "liquid_staking"), `product_id` (set to "stakestonev1"), `chain` (set to "ethereum"), and `user_type` classification

### Final aggregation
- **Combining components**: Unions withdrawal and deposit user interactions into a single dataset containing all StakeStone protocol interactions, preserving user type distinctions and temporal information
- **Time aggregation**: Truncates block timestamps to day boundaries using day-level granularity to group all transactions within the same calendar day. This ensures users are counted once per day regardless of multiple transactions
- **Final calculation**: Counts distinct user addresses per day by applying distinct selection on the `user_address` field after timestamp truncation. Users who perform multiple transactions (deposits, withdrawals, or both) on the same day are counted only once in that day's DAU
- **Data quality**: Applies chain availability filtering to ensure consistent data availability across the reporting period and excludes periods where blockchain data may be incomplete or unreliable

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

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

StakeStoneSTO

Active users (daily)

Active users (daily)

Competitive landscape

Chain breakdown