Collators aggregate parachain transactions block candidates and producing state transition proofs for validators based on those blocks.

Heima is a specialized identity and data verification blockchain powered by Polkadot Relay chain.

HEI holders own and govern the protocol. Heima’s investors include LD Capital, Digital Renaissance, Signum Capital, and others.

website

twitter

github

discord

etherscan

Blockchains (L2)

Heima

# Heima Active users (daily) Methodology

## 1. Overview

Daily Active Users (DAU) for Heima measures the number of unique addresses that performed at least one transaction on the Heima network during a given day. This metric combines activity from both the native Heima substrate chain and the EVM-compatible layer, providing a comprehensive view of user engagement across both execution environments. The calculation uses distinct counting to ensure each unique user is counted only once per day, regardless of how many transactions they performed.

## 2. Data sources

The calculation relies on two primary blockchain data sources from the Heima network:

- **Native Heima extrinsics**: Substrate-based transaction records containing user identifiers and block timestamps from the core Heima blockchain
- **Heima EVM execution events**: Ethereum-compatible transaction events from the EVM layer of Heima, specifically `Executed` events from the `ethereum` pallet containing user address data in JSON format
- **Block timestamp data**: Timestamp information for precise daily boundary calculations
- **Chain metadata**: Network identifiers to distinguish between native Heima and Heima EVM activity

## 3. Step-by-step calculation

### Component A: User activity extraction
- **Purpose**: Identifies all user addresses that performed transactions on the Heima network
- **Logic**: The system processes two distinct data streams. For native Heima transactions, user addresses are extracted directly from the extrinsic `id` field, which represents the transaction sender. For EVM-compatible transactions, user addresses are extracted by parsing JSON-formatted event data from `Executed` events in the `ethereum` pallet, where the user address is stored in the first element of the event data array. Both data sources are standardized with consistent field mappings including block timestamps, chain identifiers, market sector classification as `blockchains_l2`, business segment as `blockchain`, and user type as `Transaction sender`
- **Key fields**: `block_timestamp` for timing, `id` field from extrinsics for native users, `event_data` array for EVM users, `user_address` as the standardized user identifier

### Component B: Daily aggregation and deduplication  
- **Purpose**: Aggregates user activity to daily boundaries and ensures each user is counted only once per day
- **Logic**: Block timestamps are truncated to day-level granularity using timestamp truncation to establish clear daily boundaries. The system applies distinct counting on user addresses within each day to eliminate duplicate entries when the same user performs multiple transactions. The aggregation preserves dimensional attributes including chain identifier, user type, market sector, and business segment for comprehensive reporting and filtering capabilities
- **Key fields**: `timestamp` truncated to daily boundaries, `user_address` for distinct counting, `chain` for network identification, `user_type` for categorization

### Final aggregation
- **Combining components**: The native Heima and EVM user data streams are combined using a union operation, creating a unified view of all user activity across both execution environments
- **Currency conversion**: Not applicable for this user counting metric
- **Time aggregation**: Daily boundaries are established by truncating block timestamps to day level, ensuring consistent daily reporting periods regardless of transaction timing within each day
- **Final calculation**: The final DAU value is calculated by counting distinct user addresses within each day, applying chain availability filters to ensure data quality, and supporting incremental processing with configurable lookback periods for data completeness verification

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

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

HeimaHEI

Active users (daily)

Active users (daily)

Competitive landscape

Chain breakdown