By Hyperliquid has moved its HIP-4 outcome-market infrastructure toward permissionless deployment following an August 29 network upgrade, allowing outside builders to create their own event-based markets through HyperCore.The upgrade was completed at approximately 08:39 UTC after around nine minutes of scheduled network maintenance, according to Hyperliquid’s status page.
Hyperliquid had confirmed one day earlier that HIP-4 permissionless deployments would be enabled with the next network upgrade, following weeks of testing and developer feedback. On-chain activity subsequently showed an Outcome DEX named OUT completing deployment through the HIP-4 framework, making it the first reported third-party venue registered under the new system. The deployment confirms builders can now access the infrastructure, although OUT’s registration alone does not establish that its markets have begun generating meaningful live trading volume.
Builders Need 500,000 HYPE to Deploy
Permissionless does not mean unrestricted. HIP-4 builders must stake 500,000 HYPE to operate an outcome-market deployment. At a HYPE price around $83, that represents approximately $41.5 million of tokens. The stake remains locked for at least six months and can be slashed through validator voting if a deployer creates poorly defined markets, settles an outcome incorrectly or leaves a market incorrectly unsettled for more than one week. Deployers must also settle all outstanding markets before withdrawing their stake, potentially extending the effective lock period for operators creating long-dated contracts.
Initially, each mainnet deployer is limited to 100 concurrent outcomes and 500 deployments per day. Hyperliquid expects those limits to increase rapidly toward 1,000 concurrent outcomes and 5,000 daily deployments once the infrastructure proves stable. Builders do not have complete freedom over what markets they create. Validators vote on standardized outcome templates whose specifications and semantic restrictions are stored on-chain. Once a template is approved, however, deployers can independently instantiate markets fitting those rules without requiring validators to approve every individual question. Validators can still directly create canonical markets, although Hyperliquid expects that to occur rarely.
HIP-4 Extends the Model That Powered HIP-3
HIP-4 represents Hyperliquid’s attempt to apply its builder-deployment model beyond perpetual futures. HIP-3, launched in October 2025, allowed third parties staking 500,000 HYPE to create custom perpetual markets, helping expand Hyperliquid into equities, commodities, indexes and other non-native crypto exposures. HIP-4 applies a similar model to outcome contracts.
Unlike perpetual futures, HIP-4 products are fully collateralized and have bounded payouts. They do not require funding rates or liquidations. A simple binary contract can settle at either zero or one depending on whether a predefined event occurs, allowing its market price to function similarly to an implied probability. The infrastructure can consequently support conventional prediction markets as well as bounded options-style products. Hyperliquid initially introduced HIP-4 on mainnet in May with validator-controlled markets, including recurring Bitcoin price outcomes. It later expanded into questions involving economic releases, Federal Reserve decisions, sports and other events. Permissionless deployment substantially increases the possible market universe. Rather than relying on Hyperliquid validators to decide which individual markets deserve deployment, independent operators can now compete to create products, attract liquidity and develop specialized interfaces around approved templates.
The architecture still preserves validator control over the underlying rulebook. That distinction makes HIP-4 permissionless at the deployment layer while remaining governed at the template and enforcement layers. It also creates another source of structural demand for HYPE. Every independent HIP-4 operator must lock 500,000 tokens, separately from the equivalent stake required to operate a HIP-3 deployment. If multiple specialized outcome exchanges emerge, tens of millions of dollars of HYPE could therefore be locked by each operator at current prices.
The larger strategic implication is that Hyperliquid is evolving beyond operating a single decentralized exchange. HIP-3 opened its infrastructure to third-party perpetual markets. HIP-4 now extends that approach to prediction and outcome products. If builders can attract meaningful liquidity, Hyperliquid increasingly resembles a permissionless financial-market infrastructure layer — with HYPE functioning not only as its native asset, but as the economic bond required to operate new exchanges on top of it.