Ankr operates a global network of both full and validator nodes on an array of blockchains. These nodes provide the basis for services like Ankr Staking which delegates users’ tokens to blockchain validators and delivers liquid staking rewards (supply-side fees) to users for their contributions to validation efforts.

Ankr is a web3 infrastructure provider of blockchain API/RPC connections, developer tools, and liquid staking products. Ankr was founded and launched in 2017 by Chandler Song, Ryan Fang, and Stanley Wu.

ANKR tokenholders own and govern the protocol. They currently take a cut of the total staking rewards earned by the protocol (revenue). Ankr’s investors include Binance Labs, Block VC, MapleBlock Capital, Bixin Ventures etc.

github

twitter

discord

etherscan

website

Liquid staking

Ankr

# Ankr Active users (daily) Methodology

## 1. Overview

Daily active users (DAU) measures the number of unique addresses that interact with Ankr's liquid staking protocol each day. The metric captures users who perform staking or unstaking operations across Ankr's liquid staking contracts on Ethereum (for ETH) and BSC (for BNB). This metric helps track user engagement and adoption of Ankr's liquid staking services across different blockchain networks and contract versions.

## 2. Data sources

The calculation uses parsed blockchain event logs from multiple sources:
- **Ethereum events**: Parsed `ETHStaking_StakeConfirmed` events from ETH staking contracts and `ETHStakingV2_PendingUnstake` events from ETH staking V2 contracts
- **BSC events**: Parsed `BinancePool_Staked` and `BinancePool_UnstakePending` events from BNB staking V1 and V2 contracts, plus `BinancePoolV2_Staked` and `BinancePoolV2_Unstaked` events from BNB staking V2.1 contracts
- **Blockchain metadata**: Block timestamps and block numbers for temporal aggregation and version filtering

## 3. Step-by-step calculation

### Component A: Ethereum user identification
- **Purpose**: Identifies users interacting with Ankr's ETH liquid staking contracts
- **Logic**: Extracts user addresses from Ethereum staking and unstaking events. For staking events, the `staker` field contains the user address. For unstaking events, the `receiverAddress` field contains the user address. Users are classified as either 'ETH Staker' or 'ETH Unstaker' based on the event type
- **Key fields**: `staker` for staking events, `receiverAddress` for unstaking events, `block_timestamp` for timing, `transaction_hash` and `log_index` for event identification

### Component B: BSC user identification with version handling
- **Purpose**: Identifies users interacting with Ankr's BNB liquid staking contracts across multiple contract versions
- **Logic**: Extracts user addresses from BSC staking and unstaking events, applying version-specific filtering based on block numbers. V1 contracts are used up to block 23545403, V2 contracts from block 23545403 to 28123526, and V2.1 contracts from block 28123526 onwards. For V1 and V2 contracts, the `delegator` field contains staker addresses and `claimer` field contains unstaker addresses. For V2.1 contracts, the `staker` field contains staker addresses and `receiverAddress` field contains unstaker addresses. Users are classified as either 'BNB Staker' or 'BNB Unstaker' based on the event type
- **Key fields**: `delegator` and `claimer` for V1/V2 events, `staker` and `receiverAddress` for V2.1 events, `block_number` for version filtering, `block_timestamp` for timing

### Component C: User record consolidation
- **Purpose**: Combines all user activity records from different chains and contract versions
- **Logic**: Unions together all user records from Ethereum and BSC, ensuring each user interaction is captured once with appropriate metadata including chain, user type, and market sector classification. All records are tagged with 'liquid_staking' as the market sector and business segment
- **Key fields**: `user_address` for user identification, `user_type` for activity classification, `chain` for blockchain identification, `block_timestamp` for temporal analysis

### Final aggregation
- **Combining components**: All user records from different chains and contract versions are combined into a single dataset
- **Time aggregation**: Block timestamps are truncated to day boundaries using daily granularity to group user activities by calendar day
- **User deduplication**: Within each day, user addresses are deduplicated using distinct selection to count each unique user only once per day, regardless of how many transactions they performed
- **Final calculation**: The daily active user count is the number of distinct user addresses that performed at least one staking or unstaking operation on any supported chain and contract version during each calendar day

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

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

AnkrANKR

Active users (daily)

Active users (daily)

Competitive landscape

Chain breakdown