HIP-3 changes everything: find out how. | Credit: Veronica Cestari/CCN.com
Share
Key Takeaways
Hyperliquid’s new upgrade, HIP-3, enables anyone who stakes sufficient capital to deploy perpetual futures markets on-chain independently.
Builders can launch markets directly instead of applying for listings or paying exchange fees.
The system transforms Hyperliquid from a single DEX into a permissionless market factory.
Validator coordination and transparent slashing rules will determine long-term trust.
In traditional crypto derivatives today, centralized exchanges (CEXs) or a small set of protocol operators typically act as gatekeepers: they decide which perpetual futures contracts (perps) or derivatives to list, control the parameters (leverage, liquidity incentives, oracles), and enforce risk rules.
Builders or traders must submit listing requests, pay listing or integration fees, or wait for approval.
But with Hyperliquid’s new HIP-3 (“Builder-Deployed Perpetuals”) upgrade, a bold new model emerges: any sufficiently capitalized builder can independently deploy a perpetual swap market on the Hyperliquid infrastructure, selecting oracles, fee splits, leverage limits, and more, subject only to on-chain constraints and slashing rules.
This effectively shifts power from centralized decision makers to builders, making the protocol a market factory or infrastructure layer.
Try Our Recommended Crypto Exchanges
Sponsored
Disclosure
We sometimes use affiliate links in our content, when clicking on those we might receive a commission at no extra cost to you. By using this website you agree to our terms and conditions and privacy policy.
A perpetual swap (or “perp”) is a derivative contract that tracks the price of an underlying asset but has no expiration date. Traders can hold long or short leveraged positions indefinitely (so long as margin is sufficient).
Perpetuals use a funding rate mechanism to keep the perp price aligned with the spot price. Periodically, positions pay or receive funding based on the difference between the perp and spot, transferring value between longs and shorts.
In practice, exchanges (centralized or decentralized) decide which perps to offer (e.g., BTC, ETH, altcoins, indices, exotic derivatives), set the leverage and risk parameters, integrate oracles, and manage listings or delistings.
Because listing a market requires infrastructure (order books, clearing, oracles, risk logic) and carries liability (liquidity, price manipulation, oracle failure), many emerging or niche assets never see perp markets on leading exchanges. There is friction, cost, and gatekeeping.
HIP-3 changes that dynamic by making market creation permissionless and providing certain staking and security constraints. As Hyperliquid officially describes, HIP-3 makes deployments permissionless while requiring deployers to stake and conform to on-chain rules.
What Is HIP-3? Key Mechanics
Below is a breakdown of how HIP-3 works, from the Hyperliquid documentation and external analyses.
Staking and Bond Requirement
To become a deployer (i.e., a builder who can launch perp markets), one must stake 500,000 HYPE (around $20 million).
This stake serves as a security bond. If a deployer behaves maliciously (e.g., sets faulty oracles, mismanages markets), validators can slash a portion of the stake.
When a deployer wishes to unstake, a 7-day withdrawal queue applies; during that window, the stake remains slashable if misbehavior is detected.
The documentation notes that the stake requirement may decrease over time as the infrastructure matures.
How Hyperliquid’s Hip-3 works. | Credit: Hyperliquid
This high-stakes bar serves dual purposes: it restricts market deployment to actors with serious skin in the game, and aligns incentives for responsible behavior.
Deploying a Perp Market: Responsibility and Control
Once staked, deployers can spin up their perpetual futures market (on Hyperliquid’s infrastructure) with fully independent parameters. What can the deployer choose or manage?
Market definition: The deployer chooses the oracle source, fallback logic, contract specifications (tick size, minimum price increment, margin model).
Margining, leverage, risk parameters: The maximum leverage allowed, margin ratios, and open interest caps (per market and across assets) can be configured.
Fee structure and revenue share: Deployers can add custom fees to the base fee rate and receive up to 50 % of total trading fees (i.e., a deployer-specific fee share).
Settlement and halting: They have the authority to stop trading, cancel open orders, settle all positions at mark price, and later resume or recycle a contract.
Market operations: The deployer must maintain oracle updates, manage fallback windows, monitor risk, and occasionally intervene (e.g., emergency settlement) if conditions warrant.
Each builder-deployed market behaves like a “mini exchange” plugged into Hyperliquid’s core infrastructure.
Protocol‐Level Constraints and Safety
Although deployers get great flexibility, there are built-in constraints and safety mechanisms:
Open interest caps: Per-market and global caps limit the total leverage exposure, guarding against runaway risk.
Slashing by validators: If a deployer violates protocol safety (e.g., manipulates oracles, mismanages risk), validators can slash the deployer’s stake via a stake-weighted vote.
Stake-locked until settlement: Even if the deployer halts all markets, the staking requirement remains active (for 30 days or until settlement is done).
Isolation or compartmentalization: Misbehavior in one market should not cascade; risks are isolated via caps, fallback logic, and careful oracle design.
On-chain rules and incentives: The system replaces “manual approval committees” with code-enforced guardrails. As CoinGlass frames it, HIP-3 “replaces gatekeepers with code” while preserving safety through on-chain rules and incentives.
Thus, while builders get significant freedom, they must respect the guardrails built into the protocol.
Hip-1 vs. Hip-2 vs. Hip-3. | Credit: Datawallet
Fee Dynamics and Infrastructure Sharing
Another core idea is that deployers don’t need to build all infrastructure themselves:
They plug into HyperCore, the matching engine, orderbook, execution, settlement, and risk framework shared by the protocol.
There is no need to bootstrap separate liquidity pools or set up a parallel exchange; the builder’s market shares the liquidity infrastructure.
Builders can recoup deployment costs via a fee share (up to 50%) they collect from traders.
Because infrastructure is shared, fixed costs fall, allowing more markets (especially long-tail or exotic ones) to be viable.
Hence, HIP-3 creates a marketplace for market builders, leveraging shared infrastructure to reduce friction and cost.
HIP-3 Flips the Script — Builders, Not Exchanges, Define Markets
With that design in mind, let’s examine how HIP-3 fundamentally changes who defines markets and how.
Decentralized Listing Power
Under HIP-3:
Builders, not the Hyperliquid core team or exchange operators, decide what markets to create.
They can target niche, exotic, or long-tail assets (e.g., volatility indices, synthetic assets, private company valuations, forex pairs) that traditional exchanges often ignore.
Because there is no “listing fee” gatekeeper, innovation is less restricted by bureaucratic approval. As one analysis phrased, HIP-3 “eliminates listing fees, reduces fixed costs, and allows builders to recover costs through fee sharing.”
Chainsight suggests that HIP-3 transforms Hyperliquid from a single exchange into a permissionless financial infrastructure in which deployers define markets themselves.
Thus, HIP-3 inverts traditional exchange logic: the “exchange” is no longer the central curator; instead, builders curate markets.
Modular Market Experimentation
Because builders control contract specs, they can experiment:
Tweak margin models or leverage curves to suit the volatility of that market.
Use alternative oracles, fallback logic, or feeds (e.g., on-chain data, off-chain oracles, or custom price models).
Set custom trading fees or incentive structures to attract liquidity.
Operate settlement logic differently for structured or expiring variants.
This modularity empowers experimentation: if a market fails or underperforms, the deployer can halt or recycle it, dramatically lowering the barrier to launching experimental markets.
When builders bear deployment risk and lock their capital as collateral, their incentives align with long-term, high-quality markets. They aren’t listing just for fees; they are responsible for oracle integrity, trader trust, and risk control.
Meanwhile, Hyperliquid benefits, too: the success of multiple builder markets increases overall volume, which drives protocol fee capture and token value appreciation.
In the older model, exchanges had to individually list, vet, maintain, and promote each market, and often absorb risk. HIP-3 offloads much of that to builders.
Opportunities unlocked by HIP-3
This new paradigm opens many possibilities. With permissionless deployment, markets beyond standard crypto tokens become viable:
Because the cost of launching is lower, builders may try markets that would otherwise never justify approval by large centralized exchanges.
Breakdown of Hip-3 expectations. | Credit: RTerekh X profile
Composability and Ecosystem
Builders can integrate perp markets with their own front-ends, DApps, or trading tools — creating vertical derivatives products.
Aggregators can surface multi-builder perps across the protocol, creating competition among deployers (like multiple BTC perpetual markets competing on fees, liquidity, or UI).
Infrastructure tools (analytics, risk tooling, oracle modules) may flourish to support builder markets.
Tokenomic and Value Sinks
HIP-3’s stake requirement locks up HYPE, reducing circulating supply. Nansen notes this helps position Hyperliquid similarly to how Uniswap became a permissionless spot infrastructure.
Every new market requires a HYPE bond, creating recurring demand for HYPE.
Fee capture and builder incentives further align HYPE with platform growth.
Hence, the significance isn’t just functional, but also token-economic.
The threshold of 500,000 HYPE (or even higher target levels in proposals) can restrict builders to wealthy or institutional players. Some analyses worry that this may become a centralizing filter.
Smaller teams might have to pool resources or rely on DAOs or liquid-staked HYPE to aggregate enough capital.
Over time, a few dominant deployers might control many markets, reducing diversity.
That said, this barrier is by design: it ensures only serious actors with skin in the game can deploy. It’s a trade-off between open participation and reducing attack surfaces.
Oracle Risk and Manipulation
Markets can be manipulated if a deployer selects a weak or manipulable oracle.
Because deployers maintain oracle responsibility, they need robust fallback logic, redundancy, and monitoring.
Slashing is a deterrent, but detection and governance must work swiftly.
This risk echoes past exploits (e.g., oracle-based attacks on AMMs or perps). The system must rely on technical guardrails, slashing, and community oversight.
Market Fragmentation and Liquidity Dilution
With many builder markets, liquidity may fragment across variants, hurting depth or efficiency.
A “fee war” may lead to degraded quality or unsustainable rewards if deployers set aggressive fee splits or incentives.
Some markets may be thinly traded and more fragile.
To mitigate that, good deployers will compete on quality, building liquidity incentives, and attracting market makers.
Governance Complexity
Validator slashing votes must be robust, decentralized, and careful; false or contentious slashing could undermine confidence.
Disagreements over what constitutes “malicious” behavior might escalate into governance battles.
Upgrades, parameter changes, or protocol-level modifications must balance deployer autonomy vs protocol safety.
As with any decentralized protocol, governance robustness is key.
Reputational and Counterparty Risk
If a deployer misbehaves or mishandles a market (e.g., settlement error), trust in that market may collapse.
Builders need reputation, transparency, and credible infrastructure to gain users’ trust.
Thus, reputation mechanisms, audits, and open risk disclosures become essential.
Open Questions and Future Challenges for HIP-3
While HIP-3 is live or rolling out, many open questions remain.
Will smaller teams be squeezed out? The high-stakes bar may deter smaller community projects. Much depends on whether pooling, delegated staking, or fractionalization of deployment roles emerges to let smaller teams co-launch markets.
How well will slashing governance work? Validator coordination and governance must be responsive, impartial, and robust. False positives or governance abuse could harm trust. The design will require precise definitions of misbehavior and community buy-in.
Liquidity bootstrapping challenges: Even with shared infrastructure, new markets may struggle to attract liquidity initially. Deployers may need to incentivize market makers or rebate taker fees early on, akin to liquidity mining. The economics of this will determine which markets thrive.
UX, tooling, and discovery: As many builder markets appear, traders need intuitive discovery, UX, filtering, and risk analytics. Interface design, aggregation tools, analytics dashboards, and risk tooling will become essential. Tools like QuickNode already support such functions.
Regulatory scrutiny and classification: As markets expand to real-world assets, private equities, or synthetic derivatives, regulatory scrutiny may increase (e.g., securities law, derivatives regulation). DeFi protocols must navigate compliance while preserving decentralization.
Tokenomics and sustainability: The balance between staking, fee splits, and value accrual must sustain builders and protocol. If too many markets compete on low fees, profitability may suffer. If too few markets dominate, the value grows concentrated.
Hyperliquid’s HIP-3 is a provocative and potentially transformative upgrade: it puts builders, not exchanges, in charge of defining derivative markets. By combining a high-stakes capital bond, shared infrastructure, flexible market logic, and safety constraints, HIP-3 opens the door for a new generation of decentralized perpetual futures markets.
Rather than submitting a listing request to a gatekeeper, builders can launch markets directly, provided they have the capital and responsibility to manage oracle, risk, and settlement. In doing so, HIP-3 shifts market creation from centralized curation to permissionless innovation.
If this model succeeds, the implications are broad: niche assets, exotic derivatives, private company perps, and new financial primitives may emerge more quickly. Hyperliquid may evolve into a market network where many specialized deployers compete, innovate, and serve different trader segments, all built on the same substrate.
Of course, the path is not without risks: oracle attacks, governance slashing, liquidity fragmentation, and entry barriers are real challenges. The coming months and years will test whether HIP-3 can deliver on its promise, but as it stands, HIP-3 is one of the boldest efforts yet to let builders, rather than central operators, define the future of on-chain derivatives markets.
Hyperliquid is a decentralized exchange (DEX) platform specializing in perpetual futures contracts, derivatives that allow traders to take long or short positions without expiration. It uses on-chain matching, settlement, and governance while emphasizing high performance and transparency.
What does HIP-3 stand for?
HIP-3 refers to Hyperliquid Improvement Proposal 3, also known as Builder-Deployed Perpetuals. It’s a protocol upgrade enabling independent builders to create and manage their perpetual swap markets directly on Hyperliquid’s infrastructure.
How is HIP-3 different from how markets work today?
Traditionally, centralized exchanges (CEXs) or a few protocol operators decide which perpetuals to list, set parameters, and control oracles. HIP-3 removes that gatekeeping. Any qualified builder who meets the staking requirement can deploy a market without asking permission from the exchange team.
How are safety and integrity maintained if anyone can deploy?
HIP-3 relies on on-chain constraints and validator-enforced slashing. Open-interest caps limit exposure, stakes remain locked during disputes, and malicious actions can be punished. These rules replace centralized oversight with transparent code-based governance.
Disclaimer:
The information provided in this article is for informational purposes only. It is not intended to be, nor should it be construed as, financial advice. We do not make any warranties regarding the completeness, reliability, or accuracy of this information. All investments involve risk, and past performance does not guarantee future results. We recommend consulting a financial advisor before making any investment decisions.
Giuseppe Ciccomascolo began his career as an investigative journalist in Italy, where he contributed to both local and national newspapers, focusing on various financial sectors.
Upon relocating to London, he worked as an analyst for Fitch's CapitalStructure and later as a Senior Reporter for Alliance News. In 2017, Giuseppe transitioned to covering cryptocurrency-related news, producing documentaries and articles on Bitcoin and other emerging digital currencies. He also played a pivotal role in establishing the academy for a cryptocurrency exchange website. Crypto remained his primary area of interest throughout his tenure as a writer for ThirdFloor.
Easy 
