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 Token holders Methodology

## 1. Overview

Token holders for Hydration is measured as the total number of unique addresses that maintain a non-zero balance of the project’s native asset. This metric is used by investors to track the expansion, retention, and long-term distribution of the user base on the Hydration Substrate network.

## 2. Data sources

- **Blockchain events**: `NewAccount` and `KilledAccount` events from Hydration Substrate

## 3. Step-by-step calculation

### Component A: Account lifecycle tracking

- **Purpose**: Identify the creation and removal of active addresses on the network
- **Logic**: `NewAccount` and `KilledAccount` events are extracted from the system ledger. These events represent the points at which an address first receives a balance exceeding the required existential deposit and when an address balance is reduced to zero, respectively.
- **Key fields**: `event_method` (event identification), `block_timestamp` (timing)

### Component B: Net holder change calculation

- **Purpose**: Determine the daily fluctuation in the total number of holders
- **Logic**: A numerical value is assigned to each lifecycle event, where `NewAccount` events are treated as +1 and `KilledAccount` events are treated as -1. These values are summed by day to calculate the net change in the holder base for each 24-hour period.
- **Key fields**: `daily_change` (summed net growth or contraction)

### Component C: Cumulative aggregation and refinement

- **Purpose**: Generate a continuous time series of the total holder count
- **Logic**: The daily net changes are aggregated into a running total to determine the cumulative number of unique holders for every day in the project's history. The resulting dataset is filtered to include only positive values. A forward-filling process is applied to ensure that the most recent known holder count is maintained for days where no new account lifecycle events are recorded.
- **Key fields**: `tokenholders` (final cumulative 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.

HydrationHDX

Token holders

Token holders

Competitive landscape

Chain breakdown