twitter

discord

website

github

Blockchains (L2)

peaq

# peaq Token holders Methodology

## 1. Overview

The PEAQ tokenholders metric measures the total number of unique addresses holding PEAQ native tokens at the end of each time period. This metric provides insight into the distribution and adoption of PEAQ's native token across its ecosystem. The calculation aggregates tokenholder counts from PEAQ blockchain data, applying data quality filters to ensure reliable metrics reporting.

## 2. Data sources

The calculation relies on the following data sources:

- **PEAQ blockchain data**: Native token balance records and transaction history from the PEAQ network, tracking all addresses that hold PEAQ native tokens
- **Chain availability data**: Configuration data that defines time periods and chains where data collection meets Token Terminal's quality and completeness standards  
- **Token metadata**: Information about the PEAQ native token including decimal precision and token contract details

## 3. Step-by-step calculation

### Component A: Native tokenholder extraction
- **Purpose**: Extract and prepare raw tokenholder count data from PEAQ blockchain records
- **Logic**: The system retrieves pre-calculated tokenholder counts from PEAQ native token data, which represents the number of unique addresses holding any amount of PEAQ native tokens at specific timestamps. The tokenholder count is cast to a high-precision numeric type to handle large address counts accurately
- **Key fields**: The `timestamp` field indicates the measurement time, `timestamp_grain` specifies the aggregation period (daily/weekly/monthly), `chain` identifies the PEAQ network, and `tokenholders` contains the count of unique addresses

### Component B: Metric finalization  
- **Purpose**: Apply standard Token Terminal formatting and metadata to ensure consistency across all tokenholder metrics
- **Logic**: The finalization process adds project identification metadata, standardizes field naming conventions, ensures proper data types, and applies any protocol-specific adjustments needed for PEAQ tokenholder reporting
- **Key fields**: Adds `project_id` set to 'peaq', standardizes timestamp formatting, and ensures consistent field naming across all Token Terminal tokenholder metrics

### Final aggregation
- **Combining components**: The finalized tokenholder data flows directly from the extraction step through the standardization process without additional aggregation, as tokenholder counts are already calculated at the source
- **Data quality filtering**: Chain availability filters remove time periods where PEAQ data collection was incomplete or unreliable, ensuring only high-quality tokenholder counts are included in the final metric
- **Time aggregation**: Tokenholder counts are reported at the specified timestamp grain (daily, weekly, or monthly) as determined by the source data aggregation
- **Final calculation**: The final metric value represents the exact count of unique addresses holding PEAQ native tokens at each timestamp, with no additional mathematical operations applied to the base tokenholder count

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

Unique addresses holding a non-zero balance of the project's native token.

peaqPEAQ

Token holders

Token holders

Competitive landscape

Chain breakdown