GMX and Hyperliquid use fundamentally different liquidity models — pooled counterparty vs central limit order book — with distinct implications for traders and
GMX vs Hyperliquid: Liquidity Model
GMX and Hyperliquid use fundamentally different liquidity models — pooled counterparty vs central limit order book — with distinct implications for traders and LPs.
Comparison
| Aspect | GMX | Hyperliquid |
|---|---|---|
| Liquidity model | Pooled counterparty: GLP pool acts as single counterparty to all traders | Central limit order book: makers place resting orders, takers execute against them |
| Price discovery | Oracle-based (Chainlink + custom feed); no on-chain price discovery | Order book price-time priority; on-chain price formation |
| Execution: $100K trade | Zero slippage; execution at oracle price + spread | Variable slippage depending on order book depth at price level |
| Execution: $10M trade | May hit position limits / price impact fees; large trades capped | Walks the book; deeper resting liquidity at top of book absorbs size |
| LP return source | Trading fees + trader PnL (pool profits when traders lose) | Bid-ask spread captured by market makers; HLP vault for passive LPs |
| LP risk | Toxic flow: informed traders extracting from pool | Inventory risk; adverse selection from trading against informed flow |
| MEV / frontrunning | Minimal: oracle-based execution eliminates sandwich attacks | Present: MEV searchers can front-run large orders on the CLOB |
| LP profile | Passive yield seekers who don’t want to manage positions | Professional market makers comfortable with two-sided quoting |
Analysis
GMX suits passive LPs who want oracle-priced exposure without active management. Hyperliquid suits professional market makers and traders who demand CLOB-grade execution and price discovery.