HIP-3 turned perpetual listings on Hyperliquid into something any qualified builder can do. The result is a growing set of exchanges, each with its own markets, fees and traders, all on the same chain. This guide explains what HIP-3 is, what the venue's own registry tells you, and how to read what actually trades on each DEX.
What HIP-3 is
From Hyperliquid's HIP-3 page:
- Permissionless perps. "The Hyperliquid protocol supports permissionless builder-deployed perps (HIP-3), a key milestone toward fully decentralizing the perp listing process."
- A stake behind each DEX. "The staking requirement for mainnet will be 500k HYPE", maintained for at least 183 days after the DEX is deployed, and validators can slash it by a stake-weighted vote. Each deployer that meets it can deploy one perp DEX.
- Auctions for new assets. "The first 3 assets deployed in any perp dex do not require auction participation. Additional assets go through a Dutch auction" with the same parameters as HIP-1's.
- A fee share. Deployers "can configure an additional fee share between 0-300% (0-100% for growth mode)".
What the public registry tells you
The venue's perpDexs request lists every HIP-3 DEX with its name, its deployer and its caps, and each DEX's assets with their open interest limits. It answers what exists. The live examples page shows it, keyless, in your browser.
What it does not answer is what happens there: how much each DEX trades, who trades it, what it earns, and what the next deployment slot costs.
The same DEXes, with their activity
Hypedexer indexes HIP-3 from its own nodes. One call gives the whole picture:
curl -H "X-API-Key: $HYPEDEXER_KEY" "https://api.hypedexer.com/hip3/overview"It returns the number of DEXes and assets, 24-hour volume, trades and fees, total open interest, and the state of the deployment auction. On 12 November 2026 at 00:18 UTC it read 10 DEXes, 283 assets, 5.10B USD of volume and 4.61B USD of open interest, with the auction open at 1,019.97 HYPE.
From there, each question has its route:
| Question | Route |
|---|---|
| Every DEX, or one | GET /hip3/dexs, GET /hip3/dexs/{dex_id} |
| A DEX's assets, by ticker or name | GET /hip3/assets?dex_id=…&search=… |
| Every fill, by DEX, coin, user, side or size | GET /hip3/fills |
| Candles for a HIP-3 market | GET /hip3/ohlcv?coin=… |
| Oracle prices, minute by minute | GET /hip3/oracle/stats?dex_id=… |
| Latest price and volume per asset | GET /hip3/snapshots |
| Traders per DEX or coin | GET /hip3/stats/traders |
| Leaderboard by volume, PnL, trades or fees | GET /hip3/leaderboard?by=volume |
| Open, closed and past deployment auctions | GET /hip3/auctions, GET /hip3/auctions/history |
Parameters and fields for each are in the HIP-3 reference.
Coverage
HIP-3 fills are served from 13 October 2025, and deployment auction history from 25 October 2025, both measured on Research. What each plan includes is on pricing.
For a deployer
A DEX's own numbers are the ones a deployer reports to its users and partners: volume and fees per asset, the traders who drive them, the oracle against the market. The MCP server reads the same routes in plain language, so "which HIP-3 DEX did the most volume this week?" is a question, not a script: see the MCP guide.
FAQ
What is HIP-3 on Hyperliquid? Builder-deployed perpetuals: a deployer that stakes 500k HYPE can run its own perp DEX on Hyperliquid, with its own markets and fee share.
Is there an API for HIP-3 volume and stats? Yes. GET /hip3/overview returns volume, trades, fees and open interest across all HIP-3 DEXes; per-DEX and per-asset routes break them down.
How do HIP-3 deployment auctions work? The first three assets of a DEX need no auction; each one after goes through a Dutch auction with HIP-1's parameters. GET /hip3/auctions/history lists past ones.
How far back does HIP-3 data go? Fills from 13 October 2025, auction history from 25 October 2025.