Hands-On: Launch Your Own HIP-3 Perpetual Market
Listing a perpetual market used to require an exchange's permission and a market-making desk. HIP-3 replaces the gatekeeper with a stake: anyone who locks 500k HYPE can deploy and operate their own perp DEX on Hyperliquid. The catch is that the same stake is slashable, and slashed HYPE is burned, not refunded, if your market harms the protocol. Deploying a HIP-3 market is an operator commitment, not a button you click and walk away from.
This hands-on guide walks the real requirements and decisions: the stake and its slashing rules, what you define when you create a market, how listing additional assets works, the fee split, how you operate and settle a market, and the risks that can cost you the stake. It is based on Hyperliquid's official HIP-3 specification; parameters change, so confirm the current spec before committing capital.
Key points. HIP-3 lets a qualifying deployer run one permissionless perp DEX on Hyperliquid's shared HyperCore engine. The bar is 500k HYPE staked (slashable and burned for irregular operation, even during the 7-day unstaking queue). You define the market and its oracle and operate it (set oracle prices, leverage, and haltTrading to settle). The first 3 assets need no auction; more go through a Dutch auction, plus 7 reserve slots. The deployer earns a fixed 50% fee share while users pay 2x the normal fee. Enabling cross margin on an asset is irreversible and tightly gated. Treat the oracle choice and the slashing rules as the whole game.
What it actually takes: the 500k HYPE stake
The entry requirement is a stake, not a listing fee or a pool of seed USDC. On mainnet a deployer must stake 500k HYPE, an amount expected to decrease as the infrastructure matures. Anything above the current requirement can be unstaked, and the requirement stays in force for 30 days even after you have halted all of your perps. One qualifying deployer can run one perp DEX, each with its own margining, order books, and settings.
The stake is slashable, and slashed HYPE is burned. Validators can slash a deployer through a stake-weighted vote for irregular or malicious operation, and the stake remains slashable even during the 7-day unstaking queue. As a published guideline, irregular inputs causing invalid state transitions or prolonged downtime can be slashed up to 100%, brief downtime up to 50%, and performance degradation up to 20%. Slashing does not distinguish between malicious intent, incompetence, and compromised keys; what matters is the effect on the protocol. The burned stake is not distributed to affected users.
Step 1 — Define the market
As the deployer you are responsible for two things: the market definition (including the oracle definition and the contract specifications) and the market operation (setting oracle prices and leverage limits, and settling the market when needed). HIP-3 inherits the HyperCore stack, so its high-performance margining and order books are the same as the rest of Hyperliquid, and the API to trade HIP-3 perps is unified with other HyperCore actions.
Choosing the oracle is the decision that matters most
At the protocol level the oracle is completely general, but a perp only makes sense when there is a well-defined underlying that is hard to manipulate and has real economic significance. Most price indices are not suitable. Because a deployer is subject to slashing across every market on their DEX, the oracle is not a detail to rush.
Thin oracles get a market drained. If you peg a perp to an illiquid or single-venue price, a well-capitalized attacker can push that reference, trigger liquidations in one direction, then reverse and harvest the other side. The honest test is economic: if manipulating the underlying costs less than the open interest an attacker can extract on your market, it will eventually be attacked. Use references aggregated across deep venues, and treat single-DEX feeds as unfit for leverage.
Leverage and margin are yours to set
You set the leverage limits and margin parameters, and validators do not check whether your numbers are economically sane; they only enforce protocol correctness. High maximum leverage on a thin, volatile asset will pass validation and then produce cascading liquidations the first time the price gaps. Aligning margin requirements with the underlying's real volatility is entirely your responsibility, and getting it wrong is how a market earns a bad reputation fast.
What you define / control | Notes |
|---|---|
Market definition and contract spec | Ticker, contract details, and how the market behaves. |
Oracle | General at the protocol level; choose a deep, manipulation-resistant reference. |
Leverage and margin | You set the limits; validators do not vet economic viability. |
Collateral / quote asset | Any quote asset may be the collateral; quote-asset status can be revoked by validator vote. |
Fees | Deployer share fixed at 50%; users pay 2x the usual fee. |
Step 2 — Listing assets and the auction
You do not bid for your first markets. The first 3 assets deployed in any perp DEX require no auction participation. Additional assets go through a Dutch auction with the same hyperparameters as the HIP-1 auction (including frequency and minimum price), and that auction is shared across all perp DEXs. Deployers also get 7 reserve deployments that can be used at the current auction price while bypassing the auction timer, which helps with time-sensitive launches.
Assets on your DEX | How they list |
|---|---|
First 3 assets | No auction required. |
Additional assets | Dutch auction (HIP-1 hyperparameters), shared across all perp DEXs. |
Reserve slots | 7 deployments at the current auction price, bypassing the timer. |
Step 3 — Fees, collateral, and economics
From your side, the fee share is fixed at 50%. From the user's side, fees are 2x the usual fees on validator-operated perp markets, so the protocol collects the same amount either way. The usual discounts still apply (staking discounts, referral rewards, aligned-collateral discounts), and user rebates are unaffected and do not interact with the deployer. Any quote asset can serve as a DEX's collateral, though an asset that loses permissionless quote-asset status by validator vote would disable the DEXs that depend on it.
Step 4 — Operate and settle
Deployment is one state transition; running the market is continuous. You set oracle prices, manage leverage, and watch the market's health. When you need to wind a market down, the haltTrading action cancels all orders and settles positions to the current mark price, and the same action can resume or recycle a market, which is how a deployer can list dated contracts without a fresh auction each time. Once all assets are settled, your required stake is free to unstake after the maintenance window.
Cross margin is irreversible
Enabling cross margin on an asset cannot be undone. Validators only allow cross margin on assets that meet eligibility standards: sufficient observable liquidity, a reliable external oracle, and resilience to manipulation. Every time an asset's external mark price moves more than 50% relative to the start-of-day price, validators review whether the deployer should be slashed for manipulation, and assets where 50% daily moves are expected more than once a month are ineligible for cross margin altogether. Unless you are certain, default to isolated margin.
The cold-start problem
Nothing in the protocol forces you to seed liquidity, but a perp without a deep book is useless and dangerous, and the HLP vault does not automatically allocate capital to a newly launched HIP-3 market. In practice the first participants are arbitrageurs and searchers hunting mispriced quotes, which is pure toxic flow. You need working market-making and auto-hedging before you deploy, or credible incentives for third-party makers, or the book will simply be picked apart.
Toxic flow and ADL
Because trading gas is zero, high-frequency participants can probe your resting orders cheaply, and stale quotes get adversely selected. If your liquidity depletes, spreads widen, the hourly funding swings, and in the worst case auto-deleveraging fires, force-closing profitable positions to keep the system solvent and badly damaging the market's standing. If your quoting bot does not hedge its delta on another venue, you accumulate exactly the directional exposure you were trying to avoid.
The honest risk picture
There is no automated delisting. A market that never finds organic volume becomes a ghost town of wide spreads and zero interest while you bleed fees and hedging costs, and your capital is locked behind the stake the whole time. The reassuring part of the spec is that, barring implementation bugs, slashing is expected to be rare on a cleanly operated market; the sobering part is that the system is designed for serious operators who treat the oracle, the margin, and the cross-margin switch as decisions with real, burnable consequences.
Before you deploy: a checklist
Stake and understand slashing — 500k HYPE, slashable and burned (up to 100%), even during the 7-day unstaking queue.
Pick a deep, multi-venue oracle — if manipulation costs less than extractable OI, the market will be attacked.
Set conservative leverage and margin — validators do not vet economics; the cascade risk is yours.
Default to isolated margin — enabling cross margin is irreversible and tightly gated.
Plan the asset path — first 3 free, then Dutch auction; use reserve slots for time-sensitive listings.
Build quoting and hedging before launch — the HLP will not catch your toxic flow.
Verify the current spec — parameters change; confirm on the official Hyperliquid docs.
Educational content, not investment or financial advice. Deploying and operating a HIP-3 market involves locked capital and the risk of stake slashing, and trading perpetual futures carries risk of loss. Specification details such as the staking requirement, fees, auction rules, and slashing parameters can change; always verify against the official Hyperliquid documentation before acting.
Further Reading
Hyperliquid in 6 Minutes: The Trader's Cheat Sheet from CEX to On-Chain Perps
If you can read a Binance order book, you can already trade on Hyperliquid — but the account underneath looks nothing like one. Here is what changes, and what to check first.
Leverage on Hyperliquid: How Far Are You From Liquidation, Really?
Higher leverage shortens your distance to liquidation. Here is how Cross and Isolated margin behave on Hyperliquid, what the margin ratio actually measures, and when to dial leverage back.
Perpetual Futures: Long, Short, and Realized vs Unrealized PnL
Long or short, realized or unrealized PnL, mark price and funding, explained for your first Hyperliquid perpetual trade.