Skip to main content

The universal interface for liquidity pools. hydric normalizes diverse protocol architectures (V2, V3, V4, Algebra) into this single, high-fidelity model.

Integration Strategy:

  1. Core Fields: Use for portfolio tracking, analytics, and global search.
  2. Metadata: Use for protocol-specific execution, such as calculating ticks or interacting with V4 hooks.
address
string
required

The unique on-chain identifier for the pool. - Standard: The contract address of the pool. - V4 Singleton: The unique 'poolId' (bytes32 hash) used by the Manager.

Example:

"0x8ad599c3a01ae48104127aeeb893430d0bc41221"

tokens
object[]
required

Deterministic list of assets in the pool. The array order strictly follows the protocol's internal "Token 0, 1... N" indexing.

Example:
balance
object
required

The aggregate inventory state, including Total Value Locked (TVL) and individual asset reserves.

Example:
protocol
object
required

The protocol that owns the liquidity pool and its metadata

Example:
createdAtTimestamp
number
required

Unix timestamp (seconds) of the block where the pool was created.

Example:

1768429616

chainId
enum<number>
required

The chain id where the liquidity pool is deployed. Following EIP-155 standards. Check out Chainlist to discover the chain id of any EVM Blockchain

Available options:
1,
143,
130,
999,
8453,
9745,
534352
Example:

1

type
enum<string>
required

The architectural classification of the pool. This field acts as the discriminator for the polymorphic "metadata" object.

Available options:
V3,
V4,
ALGEBRA,
SLIPSTREAM
Example:

"V3"

feeTier
object
required

Information about the fee tier of this Liquidity Pool

Example:
stats
object
required

Dynamic performance data including volume, fees, and yield aggregated over rolling time windows.

Example:
metadata
V3LiquidityPoolMetadata · object
required

Deep architectural state (Ticks, Hooks, Plugins). The schema of this object is determined by the "type" field.