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 Active addresses (monthly) Methodology

## 1. Overview

Active addresses (monthly) measures the number of unique addresses that make a transaction with Hydration. This metric tracks user engagement across both the native Substrate and EVM-compatible layers of the protocol, including products such as Hydration DEX, Hydration Lending, and HOLLAR. By capturing unique transaction signers over a 30-day rolling window, the metric provides a standardized view of monthly network adoption and activity.

## 2. Data sources

- **Blockchain events**: `Executed` events from the `ethereum` pallet and extrinsic transaction data, covering Hydration Substrate and Hydration EVM

## 3. Step-by-step calculation

### Component A: Hydration Substrate activity tracking

- **Purpose**: Identify unique users performing native operations on the Substrate chain.
- **Logic**: Transaction senders are extracted from the extrinsics data. The sender identifier is parsed and identified as the unique user address for each transaction recorded on the Substrate layer.
- **Key fields**: `block_timestamp`, `user_address` (derived from extrinsic sender)

### Component B: Hydration EVM activity tracking

- **Purpose**: Identify unique users interacting with the EVM-compatible environment.
- **Logic**: `Executed` events from the `ethereum` pallet are filtered to isolate EVM transactions. The user address is extracted by parsing the first element of the event data array, representing the transaction initiator.
- **Key fields**: `block_timestamp`, `event_data` (used to extract user address)

### Component C: Monthly aggregation

- **Purpose**: Calculate the total number of unique active users across the entire project.
- **Logic**: User addresses from both Substrate and EVM components are consolidated. A distinct count of addresses is calculated per 30-day window using UTC boundaries. The resulting values are aggregated at the chain and project levels, with zero-filling applied to any 30-day windows where no activity is recorded.
- **Key fields**: `timestamp`, `user_address`

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

Unique addresses active over a rolling 30-day window.

HydrationHDX

Active addresses (monthly)

Active addresses (monthly)

Competitive landscape

Chain breakdown