Hyperliquid HIP-3 and HIP-4 Explained: Builder Perpetuals and Outcome Markets

Hyperliquid HIP-3 and HIP-4 introduce builder-deployed perpetuals and outcome markets to the Hyperliquid protocol, according to Crypto.news. HIP-3 enables third-party builders to deploy perpetual contracts, while HIP-4 introduces outcome markets for event-based trading. The proposals involve staking mechanisms, fee structures, settlement design, and integration with platforms such as TradeXYZ, raising questions about execution risk, liquidity, and governance for crypto market participants.

Key takeaways
Hyperliquid HIP-3 enables builder-deployed perpetuals, allowing third-party developers to launch perpetual contracts on the protocol.
HIP-4 introduces outcome markets for event-based trading, expanding the protocol's product range beyond traditional perpetuals.
Both proposals involve staking, fee structures, and settlement design, which can influence protocol economics and user participation.

Table of Contents
What is Hyperliquid HIP-3?
How builder-deployed perpetuals work
What is Hyperliquid HIP-4?
How outcome markets work
Staking, fees, and TradeXYZ integration
Settlement design and execution risks
Risks and limitations
What to watch next
Frequently Asked Questions

What is Hyperliquid HIP-3?

Hyperliquid HIP-3 is a governance proposal that enables builder-deployed perpetuals on the Hyperliquid protocol, according to the source context. Builder-deployed perpetuals allow third-party developers to create and deploy perpetual futures contracts without requiring direct protocol-level approval for each new market. This design can expand the range of tradable assets and reduce the bottleneck associated with centralized market listing decisions.

For decentralized derivatives platforms, builder-deployed markets can matter because they shift control over market creation from protocol governance to individual builders, potentially increasing product diversity and innovation speed. However, this approach also introduces execution risk, liquidity fragmentation, and quality control challenges, as not all builder-deployed markets may attract sufficient trading volume or meet user expectations for reliability and settlement integrity.

How builder-deployed perpetuals work

Builder-deployed perpetuals on Hyperliquid allow developers to launch perpetual contracts by staking protocol tokens and meeting specified technical requirements, according to the source context. The exact staking amounts, collateral requirements, and approval thresholds are not detailed in the available source material, so readers should consult future protocol documentation for operational specifics.

Once deployed, builder perpetuals operate alongside protocol-native markets, sharing the same settlement infrastructure and order book technology. Builders may earn fees from trading activity on their deployed markets, creating an economic incentive to launch high-quality, liquid contracts. However, builders also bear responsibility for market design, risk parameters, and ongoing maintenance, which can influence user trust and trading outcomes.

What is Hyperliquid HIP-4?

Hyperliquid HIP-4 introduces outcome markets to the protocol, according to the source context. Outcome markets are event-based derivatives that settle based on the occurrence or non-occurrence of specific real-world events, such as election results, regulatory decisions, or macroeconomic data releases. Unlike traditional perpetuals, which track asset prices continuously, outcome markets have binary or discrete settlement outcomes tied to verifiable external events.

For crypto traders, outcome markets can provide exposure to non-price events that influence market sentiment, regulatory risk, or sector performance. However, outcome markets also introduce oracle risk, settlement dispute risk, and potential manipulation concerns, as the accuracy and timeliness of event data can directly affect settlement fairness and user confidence.

How outcome markets work

Settlement design for outcome markets typically involves a waiting period after the event occurs, during which the protocol verifies the outcome using external data feeds or community consensus. If disputes arise, governance mechanisms or designated arbitrators may review the settlement decision. The quality of settlement design can directly influence user trust, as incorrect or delayed settlements can lead to financial losses and reputational damage for the protocol.

Staking, fees, and TradeXYZ integration

Both HIP-3 and HIP-4 involve staking mechanisms and fee structures, according to the source context. Builders deploying perpetuals under HIP-3 may be required to stake protocol tokens as collateral, aligning their incentives with market quality and reducing the risk of low-effort or malicious market deployments. The source context mentions TradeXYZ as a platform integrated with Hyperliquid, but does not provide details on the specific role TradeXYZ plays in builder perpetuals or outcome markets.

Settlement design and execution risks

Settlement design is a critical component of both builder-deployed perpetuals and outcome markets, according to the source context. For perpetuals, settlement involves marking positions to market at regular intervals and ensuring that liquidations occur fairly when collateral falls below required thresholds. For outcome markets, settlement requires accurate and timely verification of event outcomes, which can be more complex than price-based settlement.

Execution risks for builder-deployed markets include liquidity fragmentation, where trading volume is spread across many low-liquidity markets, increasing slippage and reducing execution quality. For outcome markets, execution risks include oracle failures, disputed settlements, and manipulation attempts, where traders or external actors attempt to influence event outcomes or data feeds. The source context does not provide specific risk mitigation measures, so readers should evaluate these risks based on future protocol disclosures and independent analysis.

Risks and limitations

Hyperliquid HIP-3 and HIP-4 introduce several risks and limitations for protocol users and builders. Builder-deployed perpetuals may suffer from low liquidity, poor risk parameter design, or inadequate builder maintenance, leading to suboptimal trading experiences. Outcome markets face oracle risk, settlement dispute risk, and potential regulatory scrutiny, as event-based derivatives can attract attention from financial regulators concerned about prediction markets and gambling-like products.

For readers following broader crypto market news , governance proposals like HIP-3 and HIP-4 can help frame how decentralized derivatives platforms balance innovation, risk management, and user protection.

What to watch next

Readers interested in Hyperliquid HIP-3 and HIP-4 should monitor future protocol disclosures for launch timelines, staking requirements, fee structures, oracle provider details, and dispute resolution mechanisms. Governance votes on these proposals, if publicly available, can provide insight into community support and potential implementation challenges. Traders should also watch for early builder-deployed markets and outcome market launches to evaluate liquidity, execution quality, and settlement reliability in practice.

For investors evaluating decentralized derivatives platforms, HIP-3 and HIP-4 represent a shift toward more open and permissionless market creation, which can increase product diversity but also introduce quality control and risk management challenges. Comparing Hyperliquid's approach to competing platforms can help readers assess the trade-offs between centralized market curation and decentralized builder deployment.

Frequently Asked Questions

What is Hyperliquid HIP-3?

Hyperliquid HIP-3 is a governance proposal that enables builder-deployed perpetuals, allowing third-party developers to launch perpetual futures contracts on the Hyperliquid protocol without requiring direct protocol-level approval for each new market.

What is Hyperliquid HIP-4?

Hyperliquid HIP-4 introduces outcome markets to the protocol, which are event-based derivatives that settle based on the occurrence or non-occurrence of specific real-world events, such as election results or regulatory decisions.

How do builder-deployed perpetuals work?

Builder-deployed perpetuals allow developers to create and deploy perpetual contracts by staking protocol tokens and meeting specified technical requirements. Builders may earn fees from trading activity on their deployed markets, but also bear responsibility for market design and ongoing maintenance.

What are the main risks of outcome markets?

Outcome markets face oracle risk, settlement dispute risk, and potential manipulation concerns, as the accuracy and timeliness of event data can directly affect settlement fairness. Regulatory scrutiny is also a concern, as event-based derivatives can attract attention from financial regulators.

What role does TradeXYZ play in Hyperliquid?

The source context mentions TradeXYZ as a platform integrated with Hyperliquid, but does not provide details on the specific role TradeXYZ plays in builder perpetuals or outcome markets. Readers should consult future protocol updates for operational specifics.

When will HIP-3 and HIP-4 launch?

Read original source