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

## 1. Overview

Active users (monthly) measures the number of unique addresses that make a revenue-generating transaction on Hydration. This metric provides an assessment of user engagement and network adoption across both the Substrate and EVM layers of the protocol. Transaction activity is monitored for Hydration Substrate and Hydration EVM to determine the total monthly unique participant count.

## 2. Data sources

- **Blockchain events**: `extrinsics` from Hydration Substrate and `Executed` events from the `ethereum` pallet on Hydration EVM
- **External data**: Asset metadata for chain and product identification

## 3. Step-by-step calculation

### Component A: Substrate transaction sender extraction

- **Purpose**: To identify active users interacting with the Hydration Substrate layer
- **Logic**: User addresses are extracted from the `extrinsics` table for Hydration Substrate. Each address associated with a signed extrinsic is captured as a unique transaction sender.
- **Key fields**: `user_address` (sender identifier), `block_timestamp` (transaction timing)

### Component B: EVM execution tracking

- **Purpose**: To identify active users interacting with the Hydration EVM layer
- **Logic**: `Executed` events are parsed from the `ethereum` pallet on Hydration EVM. The user address is extracted from the first element of the event data array to identify the initiator of the EVM transaction.
- **Key fields**: `event_data` (containing user address), `block_timestamp` (transaction timing)

### Component C: Monthly aggregation

- **Purpose**: To calculate the final count of unique users per 30-day window
- **Logic**: Addresses from both the Substrate and EVM components are combined into a single dataset. A distinct count of these addresses is calculated over a 30-day rolling window based on UTC boundaries. Data is filtered using chain availability logic to ensure only verified and fresh data points are included in the final output.
- **Key fields**: `user_address` (unique identifier), `block_timestamp` (30-day window truncation)

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

Unique revenue-generating users over a rolling 30-day window.

HydrationHDX

Active users (monthly)

Active users (monthly)

Competitive landscape

Chain breakdown