AVSs (Autonomous Verifiable Services) reward stakers and operators in exchange for security for third party services (supply-side fees).

EigenCloud is a marketplace connecting stakers and operators with applications that need active security. EigenCloud was founded by Sreeram Kannan and launched in 2023.

EigenCloud team and investors own and govern the protocol. They do not currently take a cut of the total rewards paid by AVSs (revenue). EigenCloud's investors include Blockchain Capital, Polychain Capital, Coinbase Ventures, etc.

governance

github

twitter

discord

website

Liquid staking

EigenCloud

# EigenCloud Active users (daily) Methodology

## 1. Overview

EigenLayer daily active users (DAU) measures the number of unique user addresses that interact with EigenLayer's liquid staking protocol on any given day. This metric captures both deposit and withdrawal activities to provide a comprehensive view of daily user engagement with the protocol. The calculation identifies distinct users based on their interactions with EigenLayer's core smart contracts and aggregates them by day.

## 2. Data sources

- **EigenLayer contract events**: Parsed event logs from EigenLayer's StrategyManager and DelegationManager smart contracts on Ethereum
- **Ethereum transaction data**: Block timestamps and transaction metadata for timing and context
- **Event types captured**:
  - `Deposit` events from StrategyManager contract (identifying depositing users)
  - `WithdrawalCompleted` events from StrategyManager contract (identifying withdrawing users)  
  - `OperatorSharesIncreased` events from DelegationManager contract (identifying staking users)
  - `OperatorSharesDecreased` events from DelegationManager contract (identifying unstaking users)

## 3. Step-by-step calculation

### Component A: User interaction extraction
- **Purpose**: Identify all user addresses that interact with EigenLayer contracts and classify their activity type
- **Logic**: Extract user addresses from four specific EigenLayer contract events on Ethereum. For `Deposit` and `OperatorSharesIncreased` events, extract the user address from the `depositor` and `staker` parameters respectively and classify as 'Depositor' user type. For `WithdrawalCompleted` and `OperatorSharesDecreased` events, extract the user address from the `withdrawer` and `staker` parameters respectively and classify as 'Withdrawer' user type. Each interaction record includes the block timestamp, transaction hash, log index, and chain identifier
- **Key fields**: `user_address` (the interacting wallet address), `user_type` (Depositor or Withdrawer), `block_timestamp` (timing of interaction), `chain` (always 'ethereum'), `market_sector_id` and `business_segment_id` (both set to 'liquid_staking')

### Component B: Daily user aggregation  
- **Purpose**: Count distinct users per day across all interaction types
- **Logic**: Truncate all block timestamps to daily boundaries using day-level granularity. Group all user interactions by the truncated date and count distinct user addresses, regardless of user type or number of interactions per user. This ensures that users who perform multiple actions on the same day are only counted once in the DAU metric
- **Key fields**: `timestamp` (daily boundary), `user_dau` (distinct user address count), `timestamp_grain` (set to 'day')

### Final aggregation
- **Combining components**: All user interactions from the four event types are unioned together before daily aggregation to ensure comprehensive coverage of user activity
- **Time aggregation**: Daily boundaries are established by truncating block timestamps to day level, ensuring consistent 24-hour periods for DAU calculation  
- **Data quality filters**: Chain availability filters are applied to ensure only complete data days are included in the final metric, preventing undercount due to incomplete data collection
- **Final calculation**: The metric represents the count of unique user addresses that performed at least one interaction with EigenLayer contracts on each given day, providing a daily snapshot of protocol engagement

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

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

EigenCloudEIGEN

Active users (daily)

Active users (daily)

Competitive landscape