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 Contracts deployed Methodology

## 1. Overview

Contracts deployed measures the number of unique smart contracts published onchain within the Hydration ecosystem. This metric serves as a proxy for the volume of new infrastructure, decentralized applications, and developer activity launched on the network. By tracking the first instance a contract address appears, the metric provides insight into the growth of the Hydration EVM environment.

## 2. Data sources

- **Blockchain events**: `Executed` events from the `ethereum` pallet, covering Hydration Substrate

## 3. Step-by-step calculation

### Component A: Contract creation event extraction

- **Purpose**: Identify and extract successful smart contract deployments from the underlying Substrate chain.
- **Logic**: Successful `Executed` events are parsed from the `ethereum` pallet. The contract address and the deployer address are extracted from the event data payload. Only events with valid extrinsic identifiers and successful execution statuses are retained to ensure only valid deployments are counted.
- **Key fields**: `event_data` (containing contract and deployer addresses), `block_timestamp` (timing)

### Component B: First occurrence filtering

- **Purpose**: Ensure each smart contract is only counted once at the time of its initial deployment.
- **Logic**: The dataset is filtered to identify the minimum timestamp associated with each unique contract address. This prevents the double-counting of existing contracts and ensures the metric specifically reflects new infrastructure launches.

### Component C: Daily aggregation and product attribution

- **Purpose**: Aggregate the identified deployments into a daily time series attributed to the specific product.
- **Logic**: The number of distinct contract addresses is counted and grouped by day based on their first occurrence timestamp. The resulting values are attributed to Hydration EVM. Any days without recorded deployments are filled with zeros to maintain a continuous data series. Values are finalized following UTC day boundaries.

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

Unique smart contracts published onchain.

HydrationHDX

Contracts deployed

Contracts deployed

Competitive landscape

Chain breakdown