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

Hydration is a Polkadot parachain specialized in trading, lending, and stablecoin issuance.

HDX holders own and govern the protocol. Hydration’s investors include KR1 plc, Hypersphere, etc.

website

twitter

github

telegram

discord

medium

governance

etherscan

Blockchains (L2)

Hydration

# Hydration Number of validators Methodology

## 1. Overview

Number of validators measures the number of active nodes that produce blocks and secure the network. It reflects the degree of decentralization and resilience of the blockchain. For Hydration Substrate, this metric tracks the specific set of collators responsible for maintaining the ledger and ensuring the security of the protocol's infrastructure.

## 2. Data sources

- **Blockchain events**: `InvulnerableAdded`, `InvulnerableRemoved`, and `NewInvulnerables` events from the `collatorSelection` pallet on Hydration Substrate.

## 3. Step-by-step calculation

### Component A: Collator event extraction

- **Purpose**: To identify all historical changes to the active validator set.
- **Logic**: Events from the `collatorSelection` pallet are parsed from Hydration Substrate. Additions to the validator set are identified via `InvulnerableAdded` events, while removals are identified via `InvulnerableRemoved` events. Initial or reset validator sets are captured from `NewInvulnerables` events. Collator addresses are extracted from the event data to ensure distinct identification of each node.
- **Key fields**: `event_method` (event type), `event_data` (collator address), and `block_timestamp`.

### Component B: Validator set aggregation

- **Purpose**: To calculate the net number of active nodes on a daily basis.
- **Logic**: Distinct collators from `InvulnerableAdded` and `NewInvulnerables` events are aggregated as positive increments. Distinct collators from `InvulnerableRemoved` events are aggregated as negative increments. A cumulative sum of these changes is calculated chronologically to determine the total number of active validators at any point in time.

### Component C: Normalization and forward-filling

- **Purpose**: To provide a continuous daily time series of the validator count.
- **Logic**: The validator count is aggregated to daily granularity using UTC day boundaries. In instances where no changes to the validator set occur on a specific day, the previous day's value is forward-filled to represent the current state of the network. The final values are normalized to a numeric format for standardized reporting.

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

Number of active validators securing the network.

HydrationHDX

Number of validators

Number of validators

Competitive landscape

Chain breakdown