​
Pools & Liquidity

​
Pool Architecture

Hyperdrome uses a dual AMM design with two pool types optimized for different asset classes. The PairFactory deploys pools deterministically via CREATE2. Each pool has its own fee collection contract (PairFees) and can have a gauge attached for HDROME emissions. Every pool also includes a built-in TWAP oracle with 30-minute observation periods.

​
Volatile Pools (vAMM)

​
Stable Pools (sAMM)

​
Fee Structure

​
Swap Routing

The Router contract finds the optimal path for any token swap. It checks all available pools (both volatile and stable) and constructs multi-hop routes when a direct pair doesn’t exist or when a multi-hop path offers better execution. For example, a TOKEN_A to TOKEN_B swap might route through TOKEN_A → HYPE → TOKEN_B if it results in less slippage.

​
Providing Liquidity

1

Select a Pool

Choose a volatile (vAMM) or stable (sAMM) pool pair. Volatile pools suit uncorrelated assets; stable pools suit pegged pairs.
2

Deposit Tokens

Provide both tokens in the pair at the current pool ratio. The Router handles the math to minimize leftover dust.
3

Receive LP Tokens

You receive LP tokens representing your share of the pool. These accrue trading fees automatically.
4

Stake in Gauge

Deposit your LP tokens into the pool’s gauge to earn HDROME emissions. Unstaked LPs earn zero emissions.
Always stake your LP tokens in the gauge after depositing. Unstaked LP positions earn trading fees but miss out on HDROME emissions — which often represent the majority of yield.

​
Built-in Oracle

Every Hyperdrome pool includes a TWAP (Time-Weighted Average Price) oracle with 30-minute observation periods. This provides manipulation-resistant price feeds that can be consumed by other protocols on HyperEVM. The oracle stores cumulative price observations and can be queried for any window up to the maximum observation history.