twitter

discord

website

github

Blockchains (L2)

peaq

# peaq Active users (daily) Methodology

## 1. Overview

Daily Active Users (DAU) for Peaq measures the number of distinct user addresses that performed transactions on either the native Peaq blockchain or the Peaq EVM compatibility layer within a 24-hour period. This metric captures user engagement across both blockchain environments by counting unique transaction senders, providing insight into daily platform adoption and usage patterns. The calculation aggregates distinct user addresses from transaction activity, ensuring each user is counted only once per day regardless of transaction frequency.

## 2. Data sources

The calculation uses two primary blockchain data sources:
- **Native Peaq extrinsics**: Transaction records from the native Peaq blockchain containing transaction sender addresses and block timestamps
- **Peaq EVM events**: Ethereum-compatible transaction events from Peaq's EVM layer, specifically filtered for executed transactions with user addresses stored in JSON event data

## 3. Step-by-step calculation

### Component A: Native peaq user extraction
- **Purpose**: Identifies users from native Peaq blockchain transactions
- **Logic**: Extracts user addresses from Peaq blockchain extrinsics data using the transaction sender identifier field. Each extrinsic record contains a block timestamp and user address, representing a transaction performed by that user. All users are classified as transaction senders and mapped to the 'peaq' chain identifier.
- **Key fields**: `block_timestamp` for timing, `id` as the user address, and chain classification as 'peaq'

### Component B: Peaq EVM user extraction  
- **Purpose**: Identifies users from Peaq's Ethereum-compatible layer
- **Logic**: Extracts user addresses from Peaq blockchain events by filtering for the ethereum pallet and 'Executed' method events. These events contain JSON-formatted data where user addresses are stored in the first element of the event data array. The system parses this JSON structure to extract the executing user's address. All users are classified as transaction senders and mapped to the 'Peaq EVM' chain identifier.
- **Key fields**: `block_timestamp` for timing, parsed `event_data[0]` as the user address, `event_pallet` filter for 'ethereum', and `event_method` filter for 'Executed'

### Component C: User data standardization
- **Purpose**: Combines and standardizes user data from both blockchain layers
- **Logic**: Unions the native Peaq and EVM user data into a single dataset with consistent field structure. Applies standard metadata including market sector classification as 'blockchains_l2', business segment as 'blockchain', and user type as 'Transaction sender'. Sets product identifier as null since this metric tracks general platform usage rather than specific product adoption.
- **Key fields**: Standardized `block_timestamp`, `chain` identifier, `user_address`, and metadata fields

### Final aggregation
- **Time boundary logic**: Truncates block timestamps to day level using daily granularity, creating 24-hour boundaries aligned to calendar days
- **Distinct user counting**: Applies distinct aggregation on user addresses within each day and chain combination to ensure each user is counted only once per day regardless of transaction frequency
- **Chain separation**: Maintains separate counts for 'peaq' and 'Peaq EVM' chains while applying the same distinct counting logic to both
- **Final calculation**: The daily active user count equals the number of distinct user addresses that performed transactions within each calendar day, segmented by chain type and user classification

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

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

peaqPEAQ

Active users (daily)

Active users (daily)

Competitive landscape

Chain breakdown