website

twitter

Blockchains (L2)

Humanity Protocol

# Humanity Protocol Active users (daily) Methodology

## 1. Overview

The Humanity DAU metric measures the daily count of unique addresses that send transactions on the Humanity blockchain. This metric provides insight into daily user engagement and network activity by tracking distinct transaction senders. The calculation uses probabilistic counting methods (HyperLogLog) for efficient aggregation across multiple dimensions including total project activity, chain-level breakdowns, user type classifications, and product segmentation.

## 2. Data sources

- **Humanity blockchain transactions**: Raw transaction records from the Humanity blockchain containing transaction metadata, timestamps, transaction hashes, and sender/receiver addresses
- **Chain availability configuration**: Data quality filters and chain coverage rules to ensure consistent metric calculation across different time periods

## 3. Step-by-step calculation

### Component A: User identification and classification
- **Purpose**: Identifies and classifies unique users based on their transaction activity
- **Logic**: Extracts all transaction sender addresses from Humanity blockchain transactions. Each unique `from_address` that initiates a transaction is considered an active user. All users are uniformly classified as "Transaction sender" user type since the metric focuses on addresses that actively send transactions rather than passive recipients. The system assigns standard metadata including chain identifier ("humanity"), market sector ("blockchains_l2"), and business segment ("blockchain")
- **Key fields**: `from_address` as the user identifier, `block_timestamp` for temporal analysis, `transaction_hash` for transaction uniqueness, and classification fields like `user_type`

### Component B: Daily aggregation and distinct counting  
- **Purpose**: Aggregates transaction activity to daily boundaries and counts distinct active users
- **Logic**: Groups all transactions by day using timestamp truncation to daily boundaries. For each day, counts the distinct number of unique user addresses that sent at least one transaction. Uses standard SQL distinct counting at the daily level before passing to the next aggregation stage. Applies incremental processing logic to only recalculate recent days when new data arrives
- **Key fields**: `timestamp` truncated to day granularity, `user_address` for distinct counting, `chain` and `user_type` for dimensional grouping

### Component C: Multi-dimensional HyperLogLog aggregation
- **Purpose**: Creates efficient probabilistic distinct user counts across multiple dimensional breakdowns
- **Logic**: Initializes HyperLogLog sketches with 15-bit precision for each day's distinct user count. Creates four distinct dimensional views: total project DAU (no dimensional breakdown), DAU by chain, DAU by user type, and DAU by product. For each dimension, merges HyperLogLog sketches and extracts the final approximate distinct count. This approach enables efficient aggregation without storing individual user addresses
- **Key fields**: `hll` sketches for probabilistic counting, dimensional identifiers like `chain_id`, `product_id`, and `user_type`

### Final aggregation
- **Combining components**: Unions all dimensional breakdowns into a single result set with standardized schema including dimension type indicators and appropriate null values for non-applicable dimensional fields
- **Currency conversion**: Not applicable for this user count metric
- **Time aggregation**: Daily boundaries established through timestamp truncation, with each day representing a complete 24-hour period in the blockchain's timestamp format
- **Final calculation**: The metric value represents the approximate count of distinct user addresses that sent transactions on each day, calculated using HyperLogLog probabilistic counting with 15-bit precision for computational efficiency across large user bases

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

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

Humanity ProtocolH

Active users (daily)

Active users (daily)

Competitive landscape