Blockchain AcademicsBlockchain Academics
How HIP-3 Rewrites the Playbook for On-Chain Derivatives and Opens Hyperliquid to a New Frontier

How HIP-3 Rewrites the Playbook for On-Chain Derivatives and Opens Hyperliquid to a New Frontier

Hyperliquid’s HIP-3 upgrade enables permissionless perp DEX creation with major fee cuts and new revenue incentives for builders.

Blockchain Academics NewsroomNovember 20, 20253 min read
Share

Hyperliquid’s latest protocol upgrade, HIP-3, marks a decisive shift in how perpetual futures markets can be created and operated on-chain. The initiative introduces permissionless deployment of independent perp DEXs on the Hyperliquid blockchain, effectively opening the gates for builders who want to design and launch market venues without relying on centralized gatekeepers. By enabling new markets to begin trading with taker fees slashed by up to 90% from the network’s standard levels, Hyperliquid is betting that cost efficiency and open participation will catalyze a wave of developer-driven liquidity.

At the core of HIP-3 is a stake-based model that requires deployers to lock 500,000 HYPE to launch a single perpetual DEX. Although this threshold is expected to fall as the ecosystem matures, the mechanism serves as both a security measure and a commitment signal. Each new DEX operates as its own siloed entity, complete with dedicated order books, isolated margining, and customizable configurations. Hyperliquid has also hinted that future iterations may allow multiple DEXs to function under one consolidated stake, broadening the economic incentives for builders who intend to scale.

Market creation under HIP-3 follows a tiered listing structure. The first three assets deployed within a DEX can be listed without an auction, while any additional markets must pass a shared Dutch auction process, a design that helps prevent spam deployments and ensures alignment between market creators and participants. For now, only isolated margin is supported, but the roadmap outlines cross-margin capabilities and more sophisticated tooling that will help DEX operators manage collateral and risk with greater precision.

One of the upgrade’s most notable elements is its revenue-sharing framework. Hyperliquid has introduced a builder-first model that grants deployers 50% of all trading fees generated by their markets. User discounts remain active, though HIP-3 markets charge fees that are twice those of validator-run perps. This model, combined with deeply reduced taker fees at launch, is crafted to make market creation both economically appealing and structurally sustainable. Upcoming enhancements—such as fee configurability, asset-reservation improvements, and better collateral migration mechanisms for markets affected by changes in quote-asset status—signal Hyperliquid’s commitment to long-term composability.

Yet HIP-3’s ambitions reach beyond crypto-native assets. By enabling flexible derivatives infrastructure, Hyperliquid is laying the groundwork for markets tied to equities, commodities, and potentially other real-world assets. The team has positioned the upgrade as a catalyst for new on-chain financial instruments, arguing that decentralized venues could eventually become legitimate alternatives to traditional derivatives exchanges. This vision aligns with a broader industry trend: developers are increasingly seeking permissionless environments where they can experiment, deploy, and earn from market creation without navigating institutional bottlenecks.

HIP-3 arrives at a moment when lower fees, rising developer engagement, and expanding asset classes are reshaping the competitive landscape of decentralized finance. By blending accessibility with economic incentives, Hyperliquid aims to accelerate the proliferation of on-chain derivatives and redefine what can be traded in a trust-minimized environment. If the upgrade succeeds in attracting a new generation of market builders, HIP-3 may become one of the most influential steps in the platform’s evolution—and in the broader shift toward open financial infrastructure.

Discussion

Loading comments...