Hyperliquid’s core contributors are actively seeking feedback on the latest testnet template on HIP-4, its standard for outcome and prediction markets, which is moving toward permissionless deployment. HIP-4 went live on Hyperliquid mainnet in May 2026, introducing outcome trading as an extension of Hyperliquid’s derivatives toolkit. As per a post by 0xMaxs, core contributor Xulian is asking the community to evaluate the existing template design before the templates move to validator review and an on-chain vote. The process could eventually allow approved templates to be written to mainnet and used by deployers once permissionless deployment reaches mainnet.
The feedback stage is necessary because the templates will determine which market types deployers can create under HIP-4. With several structures being evaluated, the current phase is focused on refining those structures before they can move towards mainnet approval.
What is the HIP-4 Template Update?
The latest development focuses on the HIP-4 testnet template, which is created to facilitate standardized structures for deploying outcome prediction markets. The template can be accessed through on-chain queries or the testnet API. Each template family uses an incrementing integer suffix to identify its latest version. As per the information, the testnet currently contains 16 template records, including older versions. When only the highest version from each template family is counted, there are approximately 12 latest templates covering seven different market structures.
On testnet, developers stake 100 HYPE to register as an outcome deployer, with no auction or gas fee. Each deployer is capped at 10 active outcomes and 50 deployments per day. Hyperliquid’s preliminary mainnet proposal sets a far higher bar, requiring 500,000 HYPE staked and locked for six months. Validators can partially or fully slash that stake if a market is poorly defined, settled incorrectly, or left unresolved for more than a week. Deployers can earn up to 50% of the trading fees their markets generate.
The current structures include expiry cost markets, which use TWAP settlement over a specified period, as well as touch price markets and range yield markets. Other templates cover event-based outcomes, including central bank decisions, sports binary choices, and sports win-draw-loss markets. The range of templates shows HIP-4 is being built to support different types of outcome markets rather than one single format. By standardizing templates, Hyperliquid can give deployers with predefined structures that can be assessed before they are made feasible for market creation.
However, the present templates remain on the testnet. The mainnet and deployer list are still empty, meaning no templates have yet been approved for permissionless use on mainnet at this stage.
Who Will Approve HIP-4 Templates and When Can Markets Launch?
The existing process starts with community review on the templates. Xulian is publicly soliciting that review before the proposals proceed towards the next stage. After the feedback window, validators will assess the templates and vote on them on-chain. Only templates that are approved will be written to the mainnet and made available for use by deployers. The procedure creates multiple stages between designing and actually deploying a prediction market.
Community members first have a chance to give feedback, followed by validator evaluation and an on-chain vote. Approved templates can be written on the mainnet, after which deployers can use them to build markets. Approval alone does not mean a market can launch.
As per the information, all template instantiations depend on permissionless deployment reaching mainnet. This means that the present testnet activity should be viewed as a foundation for a potential mainnet launch rather than an indication that permissionless prediction markets are already active under HIP-4. The structure also gives validators a decisive role in determining which market templates become part of the mainnet framework. Rather than allowing every proposed structure to be deployed, the procedure needs templates to pass through community and validator approval first.
The mainnet launch remains reliant on multiple decisions rather than a single approval. Even after the templates are assessed, HIP-4 must be enabled before deployers can instantiate markets using those templates.
As of now, Hyperliquid’s focus remains on refining the template system and collecting feedback. With several market structures already represented on the testnet, the next steps are validator review, an on-chain vote, and a decision on enabling permissionless deployment on mainnet. If the process moves ahead as mentioned, approved templates could give deployers with standardized building blocks for launching a broader range of prediction markets and outcomes on Hyperliquid.
