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)
| Property | Value |
|---|---|
| Curve | x * y = k (constant product) |
| Default Fee | 0.2% |
| Naming Convention | vAMM-TOKEN0/TOKEN1 |
| Best For | Uncorrelated pairs (HYPE/USDC, HDROME/HYPE) |
Stable Pools (sAMM)
| Property | Value |
|---|---|
| Curve | x³y + y³x = k (StableSwap variant) |
| Default Fee | 0.02% |
| Naming Convention | sAMM-TOKEN0/TOKEN1 |
| Best For | Pegged/correlated pairs (USDC/USDT, HYPE/stHYPE) |
Fee Structure
| Parameter | Detail |
|---|---|
| Volatile Pool Fee | 0.2% (adjustable by Fee Manager) |
| Stable Pool Fee | 0.02% (adjustable by Fee Manager) |
| Fee Recipient | 100% to veHDROME voters of that pool’s gauge |
| Fee Collection | Collected per swap into PairFees contract |
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
Select a Pool
Choose a volatile (vAMM) or stable (sAMM) pool pair. Volatile pools suit uncorrelated assets; stable pools suit pegged pairs.
Deposit Tokens
Provide both tokens in the pair at the current pool ratio. The Router handles the math to minimize leftover dust.
Receive LP Tokens
You receive LP tokens representing your share of the pool. These accrue trading fees automatically.