HIP-3 is Hyperliquid's permissionless perpetuals standard. It lets any qualified deployer spin up a new perp market on HyperCore by staking HYPE, defining the oracle and risk parameters, and earning a share of trading fees as the market grows.

How much HYPE does it take to deploy a HIP-3 market?

HIP-3 uses a Dutch auction plus a rolling stake requirement. Deployers lock a large amount of HYPE (in the hundreds of thousands to low millions range depending on demand) for the right to operate a perp, and the stake is slashable if risk parameters are abused.

How is HIP-3 different from Hyperliquid's core perps?

Core Hyperliquid perps are listed by the protocol team and share a single risk engine. HIP-3 markets are deployed by third parties with isolated risk, custom oracles, and their own fee splits — similar to how HIP-1 enabled permissionless spot listings.

Who benefits from HIP-3?

Builders unlock long-tail markets (pre-IPO equities, prediction markets, niche alts, RWAs). Traders get deeper selection without leaving Hyperliquid. HYPE stakers benefit from extra fee flow and demand for the token as collateral to deploy markets.

HIP-3: Hyperliquid Permissionless Perps Guide 2026

Hyperliquid spent 2024–2025 becoming the dominant on-chain perp venue by out-engineering everyone on latency, UX, and liquidity. HIP-3 is the next act: a permissionless standard that lets anyone — not just the core team — deploy a new perpetual market on HyperCore. This guide breaks down how HIP-3 works, what it costs to deploy, who should care, and why it is the most consequential change to on-chain derivatives in 2026.

1. The one-paragraph version

HIP-3 is to perps what HIP-1 was to spot. A qualified deployer wins the right to operate a new perp market through a Dutch auction, locks a large HYPE stake, and defines the oracle source, margin schedule, tick size, and fee split. The market then lives inside HyperCore with isolated risk from the protocol-operated book. If the deployer misbehaves — bad oracle, negligent risk parameters — their stake is slashable. If the market succeeds, the deployer earns a share of taker fees forever.

2. Why HIP-3 exists

Hyperliquid's core listing pipeline is a bottleneck. The protocol team has been conservative — and rightly so — about which assets get a perp, because every listing shares the same HLP vault and risk engine. That conservatism leaves real demand on the table: long-tail alts, pre-IPO equities, prediction markets, tokenized treasuries, ecosystem points. Every listing the team declines is liquidity that flows to CEXes or dies on a worse venue. HIP-3 externalizes listing decisions to a market of builders while keeping the matching engine, margining math, and settlement centralized on HyperCore.

3. How HIP-3 deployment works

The mechanics are elegant: a rolling Dutch auction determines the right to deploy one new market per epoch. The winning bidder locks HYPE as collateral against the market they operate. They define:

The underlying asset and oracle source (Pyth, internal TWAP, or a custom attested feed).
Margin schedule and max leverage (bounded by protocol-wide caps).
Tick size, lot size, and funding rate curve.
The taker-fee share routed back to the deployer (builder fee), and the share that flows to HLP and the Assistance Fund.

Once deployed, the market appears on Hyperliquid's frontend and API alongside every other perp. Traders interact with it exactly as they would with a core market. Behind the scenes, the deployer's stake is the first-loss capital if oracle manipulation or risk-parameter negligence causes a socialized loss.

4. The HYPE demand loop

HIP-3 creates a new, structural sink for HYPE that is not speculative. To run a market, you must lock HYPE. To keep running it as volume grows, you may need to add more HYPE to maintain your stake-to-open-interest ratio. Every successful HIP-3 market is, in effect, HYPE taken out of circulation and collateralized against real trading activity. Combined with the Assistance Fund's ongoing HYPE buybacks from fee revenue, this is one of the tightest token-economic loops in crypto: more volume → more fees → more buybacks → more HYPE needed to deploy the next market → less float → more volume.

5. What traders get

For traders, HIP-3 should feel invisible. The UX is the same orderbook, same wallet, same HLP-backed liquidity model. What changes is selection. Expect long-tail perps on assets that no centralized venue bothers with: governance tokens of mid-cap L2s, liquid-staking derivatives, RWA indices, maybe even perpetual markets on off-chain benchmarks like the VIX or pre-IPO shadow prices. The risk engine is isolated, so a blow-up in a niche HIP-3 market cannot cascade into HLP or the core book.

6. What builders get

HIP-3 is the first credible way to run a perp DEX without building a perp DEX. If you are a team that understands a specific vertical — sports prediction, RWA yield, a particular ecosystem's token gravity — you can deploy a market, market it to your community, and collect builder fees without ever writing matching-engine code. This is to derivatives what Uniswap v4 hooks were meant to be: a platform for specialization. The difference is that Hyperliquid already has the users.

7. Risks and open questions

HIP-3 is not risk-free. The three things to watch in 2026:

Oracle hygiene. Deployers pick oracles. Bad oracle selection on an illiquid underlying is how you get a nine-figure loss on a six-figure market.
Stake calibration. If the required HYPE stake is too low relative to open interest, a rational attacker can deploy a market specifically to exploit it. Too high and no one deploys.
Regulatory surface. Permissionless perps on tokenized equities will draw regulatory attention in a way the spot side never did. Expect jurisdictional gating at the frontend level.

8. Comparison: HIP-3 vs. the alternatives

The obvious comparisons are dYdX v4 (appchain with permissioned listings), GMX v2 (pool-based, no orderbook), and Drift on Solana (hybrid DLOB). None of them are permissionless at the listing layer today. Aevo has flirted with the idea via its pre-launch markets, but those remain curated. HIP-3 is the first production standard that lets an outside team deploy a market on a top-three venue with real liquidity already present.

9. How to watch HIP-3 in the wild

Three things to monitor: the auction clearing price (a proxy for builder demand), the ratio of HIP-3 volume to core volume (adoption), and the slashing event count (risk hygiene). If in six months HIP-3 volume is 10%+ of Hyperliquid's total and there have been zero slashings, the standard is working. If either number goes the wrong way, expect parameter changes.

10. Bottom line

HIP-3 is the moment Hyperliquid stops being a perp DEX and becomes a perp platform. The core team has effectively said: we will build the best matching engine and risk infrastructure in crypto, and we will let the market decide which assets deserve a perp. For HYPE holders, it is a new demand sink. For builders, it is the lowest-friction way to run a derivatives business. For traders, it is more markets with the same UX. It is the rare change that is net-positive for every stakeholder at once — which, in crypto, usually means it is going to matter.

Frequently asked questions

Is HIP-3 live today?

As of April 2026, HIP-3 is in its rollout phase with the first cohort of builder-deployed markets going live on HyperCore. Expect the standard to be fully permissionless after the initial parameter-tuning epochs.

Do I need to do anything as a HYPE holder?

No action required. The Assistance Fund continues to buy back HYPE from fee revenue, and HIP-3 adds a new structural demand source. If you want to participate directly, you can delegate HYPE toward deployer bids once that feature ships.

Can anyone deploy a HIP-3 market?

Technically yes, but the Dutch auction and stake requirements make it a serious commitment. Expect early deployers to be specialist teams, not individuals.