All articles
HIP-3 risks Hyperliquid6 min readReviewed 2026-09-04

HIP-3 Markets: Risks for Traders on Builder-Deployed Perps

What traders should check before using a HIP-3 builder-deployed perp market: deployer role, oracle duties, fees, margin, and what the HYPE stake does not cover.

Direct answer

HIP-3 lets a deployer who stakes 500,000 HYPE run their own perp DEX on Hyperliquid, setting markets, fees, and oracle updates. For traders that means each market has its own operator, so check who the deployer is, how the oracle is set, what the fee scale and open-interest cap are, and how settlement works. The stake is not a guarantee against losses.

Updated 2026-10-043 sourcesAffiliate action disclosed in the site header

In short

  1. 1Each HIP-3 DEX has its own deployer, oracle setters, and fee settings.
  2. 2The 500,000 HYPE stake creates accountability but is not a reimbursement fund.
  3. 3Check fees, caps, margin mode, and settlement terms before trading a new market.
Risk notice
Crypto perpetuals and leveraged trading are high risk. You can lose money through liquidation, funding, slippage, oracle issues, protocol failures, and market volatility.

What is a HIP-3 market?

HIP-3 allows builders to deploy perpetual markets, including stock-like and other assets, on Hyperliquid infrastructure. The deployer configures markets, sets fees within the rules, and is responsible for oracle updates and settlement.

What does the 500,000 HYPE stake do?

A mainnet deployer must maintain 500,000 HYPE and can face slashing for misbehaviour; the stake stays required for a minimum period after deployment. It aligns incentives, but the docs do not describe it as compensation for trader losses, so do not treat it as insurance.

Why does the oracle matter?

Oracle setters publish the prices used for marks, funding, and liquidation. A stale or wrong oracle can liquidate positions that the underlying market would not. Look at who sets prices and how often they update.

How do fees and caps differ?

HIP-3 deployers can adjust fees through a fee scale, and growth mode can reduce them. Open-interest caps limit exposure per market. Compare the fee after scale with the main venue, and read the cap before sizing.

What should I verify first?

Open the DEX page, read the deployer and fee recipient, the collateral token, the leverage, and the recent configuration changes. If any of that is unclear, size down or skip the market.

Example: reading a new HIP-3 market

Say a new stock-like HIP-3 market appears with attractive volume. Before trading, open its DEX page: note the deployer, the fee recipient, the fee after scale, the open-interest cap and how much is used, and any recent configuration changes.

If the cap is nearly used, new positions may be limited. If the deployer changed fees last week, check why. If you cannot find the oracle setters, size down or skip.

Common mistakes

Use the DEX page as a checklist and compare settings with the main perps.

  • Assuming every HIP-3 market follows the main venue's settings.
  • Treating the HYPE stake as insurance.
  • Ignoring caps and fee scale.

Practical next steps

Make the DEX page your first stop for any HIP-3 market. Read the deployer, the fee recipient, the fee after scale, the open-interest cap and its use, the collateral token, and the recent configuration changes. Then compare with a main-venue market of similar size and note every difference. If you cannot explain a difference, reduce size. The HIP-3 directory on this site lists active DEXs with their markets, and the HIP-3 API guide shows how to read the same fields directly from the public endpoints.

Next useful check

Apply this before you trade

Sources

3 references · Expand
  • Supports: HIP-3 builder-deployed perp mechanics, deployer responsibilities, 500,000 HYPE staking requirement, minimum stake duration, deployment rules, configurable fees, settlement, oracle duties, slashing risk, cross margin, and backstop liquidation.
  • Hyperliquid Docs: FeesAccessed 2026-08-26
    Supports: Rolling 14-day volume tiers, perps and spot fee schedules, HIP-3 deployer fee scale and growth mode, strict HYPE staking-tier thresholds and discounts, referral fee formula and limits, staking-account linking risks, fee-model caveats, fee distribution to HLP, the assistance fund, and deployers, the assistance fund system address, and burn recognition of assistance-fund HYPE.
  • Supports: Core and HIP-3 perpetual DEX discovery, current market contexts including rolling dayNtlVlm, perpetual metadata, funding history, predicted funding, DEX and market limits, DEX status, configuration metadata, clearinghouse state, and open-interest cap fields.

Keep reading

Related Hyperliquid questions