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 Number of validators Methodology

## 1. Overview

The number of validators metric tracks the daily count of unique validators who authored blocks on the Heima blockchain. This metric measures network decentralization and validator participation by counting how many distinct validators were active in block production each day. The calculation uses blockchain consensus data to identify unique block authors and aggregates them by day.

## 2. Data sources

- **Heima blockchain block data**: Raw block records from the Heima blockchain containing block metadata and validator information
- **Block consensus data**: Each block includes the `author_id` field identifying the validator who proposed the block, along with timestamps and block numbers
- **Blockchain infrastructure data**: Native blockchain data captured during the block production and consensus process

## 3. Step-by-step calculation

### Component A: Block data extraction
- **Purpose**: Extract and prepare raw block data from the Heima blockchain
- **Logic**: Raw block data is retrieved from Heima blockchain records, including block timestamps, validator author identifiers, and block numbers. The data is cast to appropriate types with `timestamp` converted to timestamp format, `author_id` cast as string, and `number` (block number) cast as integer. This ensures data consistency and proper formatting for downstream processing.
- **Key fields**: `block_timestamp` for timing, `author_id` for validator identification, `block_number` for sequencing

### Component B: Daily validator aggregation  
- **Purpose**: Count unique validators active each day
- **Logic**: Block timestamps are truncated to daily boundaries to group all blocks by day. For each day, the calculation counts distinct `author_id` values to determine how many unique validators authored blocks. This aggregation includes metadata fields for `timestamp_grain` set to 'day', `product_id` set to 'heimachain', and `chain_id` set to 'heima' for standardized metric formatting.
- **Key fields**: Truncated daily `timestamp`, distinct count of `author_id` as `number_of_validators`

### Final aggregation
- **Combining components**: The daily validator counts are processed through the `finalize_metric_number_of_validators` macro which standardizes the metric format and applies data quality rules
- **Fill strategy**: A 'fill_forward' strategy is applied to handle days where no blocks were produced, carrying forward the last known validator count to maintain continuity
- **Data quality filtering**: Chain availability filters are applied to ensure the data meets quality standards before final output
- **Final calculation**: The result provides daily counts of unique validators who were active in block production, representing the level of validator participation and network decentralization on each day

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

Number of active validators securing the network.

HeimaHEI

Number of validators

Number of validators

Competitive landscape

Chain breakdown