website

twitter

Blockchains (L2)

Humanity Protocol

# Humanity Protocol Active addresses (daily) Methodology

## 1. Overview

Active addresses daily measures the number of unique wallet addresses that initiated at least one transaction on the Humanity blockchain each day. This metric serves as a proxy for daily active users and protocol adoption, tracking engagement levels by counting distinct transaction senders rather than transaction volumes.

The calculation uses HyperLogLog (HLL) data structures for efficient distinct counting across large datasets, enabling flexible dimensional breakdowns while maintaining computational efficiency.

## 2. Data sources

- **Humanity blockchain transaction records**: Raw transaction data containing transaction hashes, block timestamps, and sender addresses (`from_address`)
- **Chain availability configuration**: Data governance rules that filter results based on chain data completeness and reliability standards

## 3. Step-by-step calculation

### Component A: User transaction extraction
- **Purpose**: Extract and standardize user activity data from raw Humanity blockchain transactions
- **Logic**: Pull transaction records from Humanity blockchain data, casting `block_timestamp` to timestamp format, `transaction_hash` to string, and `from_address` to string. Each transaction is classified with static metadata: 'humanity' as chain identifier, 'blockchains_l2' as market sector, 'blockchain' as business segment, and 'Transaction sender' as user type. No product-level segmentation is applied (product_id is null).
- **Key fields**: `block_timestamp` (when transaction occurred), `from_address` (wallet address initiating transaction), `transaction_hash` (unique transaction identifier)

### Component B: Daily user identification
- **Purpose**: Calculate daily distinct active users by aggregating unique addresses per day
- **Logic**: Group transaction data by day using timestamp truncation to day boundaries. For each day, identify unique user addresses that sent at least one transaction. Apply incremental processing logic to only process recent data during updates, looking back from the maximum partition date. Each record represents one unique user address active on a specific day.
- **Key fields**: `timestamp` (day-level date), `user_address` (unique sender address), `timestamp_grain` (always 'day' for daily metrics)

### Component C: HyperLogLog aggregation and dimensional breakdown
- **Purpose**: Create efficient distinct count aggregations across multiple dimensional breakdowns using HyperLogLog data structures
- **Logic**: Initialize HLL sketches for each user address within daily partitions, then merge these sketches across different dimensional groupings. Create four dimensional breakdowns: project-level aggregation (combining all activity), chain-level aggregation (by blockchain), user-type aggregation (by sender classification), and product-level aggregation (currently not segmented). Use HLL merge operations to combine sketches and extract final distinct counts for each dimension.
- **Key fields**: `hll` (HyperLogLog sketch for distinct counting), `dimensions` (breakdown type: 'project_dbt_tag', 'chain', 'user_type', 'product_id'), `user_dau` (distinct user count extracted from HLL)

### Final aggregation
- **Combining components**: Union all dimensional breakdowns (project, chain, user type, product) into a single result set, maintaining separate records for each dimensional view of the same underlying daily activity
- **Currency conversion**: Not applicable - this metric counts addresses, not monetary values
- **Time aggregation**: Daily boundaries are established by truncating timestamps to day level, with missing days filled with zero values to ensure complete time series continuity
- **Final calculation**: Rename the `user_dau` field to `active_addresses_daily` to align with blockchain analytics naming conventions. Apply chain availability filters to exclude data from periods when the blockchain had incomplete data coverage. The final metric represents the count of unique wallet addresses that initiated at least one transaction on each day.

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

Unique active addresses over a fixed 24-hour window.

Humanity ProtocolH

Active addresses (daily)

Active addresses (daily)

Competitive landscape