Aleph Zero EVM is powered by Arbitrum's AnyTrust protocol which uses a data availability committee (DAC) to store raw transaction data.

Aleph Zero EVM is an Ethereum layer 2 powered by Arbitrum Orbit tech stack. This dashboard does not include Aleph Zero WASM data.

AZERO tokenholders own and govern the protocol.

github

twitter

discord

website

Blockchains (L2)

Aleph Zero EVM

# Aleph Zero EVM Token holders Methodology

## 1. Overview

The AlephZero token holders metric measures the total number of unique addresses holding non-zero amounts of the native AlephZero token on the AlephZero EVM network. This metric tracks token distribution and adoption by counting distinct wallet addresses that maintain balances of the native token over time. The calculation provides a time-series view of token holder growth, aggregated at regular intervals to show network adoption trends.

## 2. Data sources

The calculation relies on the following data sources:
- **AlephZero EVM blockchain data**: Transaction records and account state data from the AlephZero EVM network
- **Native token balance data**: Account balance snapshots showing native token holdings across all addresses
- **Transaction traces**: AlephZero EVM transaction execution data to track balance changes
- **Account state information**: Current and historical balance states for addresses on the network

## 3. Step-by-step calculation

### Component A: Native token holder identification
- **Purpose**: Identifies all unique addresses that hold non-zero amounts of the native AlephZero token
- **Logic**: The calculation processes AlephZero EVM blockchain data to identify addresses with native token balances. It extracts account balance information, filtering for addresses that hold positive amounts of the native token. The data is aggregated by time periods to create time-series snapshots of token holder counts.
- **Key fields**: The process captures `timestamp` for time-series tracking, `timestamp_grain` for aggregation periods, `chain` identifier for the AlephZero EVM network, and `tokenholders` count representing the number of unique addresses

### Component B: Data precision and standardization  
- **Purpose**: Ensures numerical precision and applies standardized formatting for the metric
- **Logic**: The raw token holder count is converted to high-precision numeric format to maintain accuracy. The data undergoes standardization through the finalization macro, which applies consistent metadata, formatting, and metric identification specific to AlephZero.
- **Key fields**: The `tokenholders` field is cast to `bignumeric` type for precision, and the metric receives a `data_id` of 'alephzero' for identification

### Final aggregation
- **Combining components**: The standardized token holder data flows through the finalization process, which applies Token Terminal's standard metric formatting and metadata
- **Time aggregation**: Data is aggregated by timestamp grain, likely daily intervals, to provide consistent time-series measurements
- **Data quality controls**: A temporal filter excludes any data beyond September 17, 2025, preventing future date artifacts from affecting the calculation
- **Final calculation**: The result is the count of unique addresses holding non-zero native AlephZero token balances, presented as a time-series metric showing token holder growth over time

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

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

Aleph Zero EVMAZERO

Archived

Token holders

Token holders

Competitive landscape

Chain breakdown