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

Phala is a specialized privacy-preserving cloud computing blockchain powered by Polkadot Relay chain.

PHA holders own and govern the protocol. Phala’s investors include IOSG Ventures, Incuba Alpha, Candaq Fintech Group, and others.

website

twitter

discord

github

etherscan

Blockchains (L2)

Phala

# Phala Number of validators Methodology

## 1. Overview

The number of validators metric measures the count of unique active validators on the Phala network on a daily basis. This metric provides insight into network decentralization and validator participation trends by tracking how many distinct validator addresses are active each day. The calculation aggregates validator registry data with blockchain timestamps to produce daily validator counts.

## 2. Data sources

The calculation relies on two primary raw data sources from the Phala blockchain:

- **Phala validator registry data**: Contains validator address information and associated block numbers, representing when validators were active or registered on the network
- **Phala blockchain block data**: Provides block timestamps and block numbers that enable time-based aggregation of validator activity

## 3. Step-by-step calculation

### Component A: Validator aggregation
- **Purpose**: Aggregates unique validators by timestamp from raw validator registry data
- **Logic**: The system joins validator registry records with block data using block numbers as the common key. Each validator record contains a validator `address` and associated `block_number`. By joining with block data, each validator gets associated with a specific `block_timestamp`. The data is then grouped by timestamp, and distinct validator addresses are counted within each time group to determine how many unique validators were active at each point in time.
- **Key fields**: Validator `address` for uniqueness identification, `block_number` for temporal association, `block_timestamp` for time-based grouping

### Component B: Daily standardization  
- **Purpose**: Converts raw timestamp-based counts to standardized daily metrics
- **Logic**: Raw validator counts are aggregated to daily boundaries by truncating timestamps to day granularity. When multiple records exist for the same day, the system applies a window function to deduplicate by selecting the record with the latest timestamp within each day. This ensures each day has a single representative validator count value.
- **Key fields**: Daily truncated `timestamp`, deduplicated `number_of_validators` count

### Final aggregation
- **Combining components**: The daily validator counts flow directly from the aggregation component to the standardization component without additional joining
- **Currency conversion**: Not applicable for this count-based metric
- **Time aggregation**: Data is standardized to daily boundaries with deduplication handling for multiple same-day records
- **Final calculation**: The final metric represents the count of distinct validator addresses active on the Phala network for each day, with metadata formatting applied including market sector classification as blockchain layer 1, business segment as blockchain, and chain identification as Phala. A zero-fill strategy handles missing data periods to ensure continuous time series coverage.

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

Number of active validators securing the network.

PhalaPHA

Archived

Number of validators

Number of validators

Competitive landscape

Chain breakdown