✳flâneur — a map of the web's best reading

HIP-3: Builder-Deployed Perpetuals | Hyperliquid Docs

hyperliquid.gitbook.io · 1,528 words · saved by 1 readers

The Hyperliquid protocol will support builder-deployed perps (HIP-3), a key milestone toward fully decentralizing the perp listing process. An MVP of this feature is live on testnet. Feedback is appreciated during this testing phase. Note that numbers and specifications below are not finalized. Builder-deployed perps share many features with HyperCore spot deployments: Deployments allocate new performant onchain orderbooks on HyperCore. Deployment gas is paid through a Dutch auction every 31 hours. A difference is that HYPE is the gas token used for perp deployments. Deployers can set a fee share of up to 50%. A difference is that the deployer can configure additional fees on top of the base fee rate. Fee share applies to the total configured fee. Deployments are fully permissionless. The deployer of a perp market is also responsible for Market definition, including the oracle definition and contract specifications Market operation, including setting oracle prices, leverage limits, and

HIP-3: Builder-deployed perpetuals | Hyperliquid Docs Hyperliquid Docs About Hyperliquid Onboarding HyperCore HyperEVM Hyperliquid Improvement Proposals (HIPs) HIP-1: Native token standard HIP-2: Hyperliquidity HIP-3: Builder-deployed perpetuals HIP-4: Outcome markets Frontend checks Trading Validators Referrals Points Historical data Risks Bug bounty program Audits Brand kit For developers API HyperEVM Nodes Powered by GitBook On this page For the complete documentation index, see llms.txt . This page is also available as Markdown . The Hyperliquid protocol supports permissionless builder-dep

Explore this link on the map →

related reading