BlockBeats News, July 20th, Hyperliquid announced that HIP-4 (Outcome Markets) is planned to support permissionless deployment in a future network upgrade and will first launch on the testnet before being rolled out to the mainnet. The team stated that similar to spot and perpetual contract markets, the technology related to outcome markets needs to undergo thorough testing in a validator deployment environment before gradually opening up to permissionless deployment to ensure system stability.
Hyperliquid stated that outcome markets have a much larger tradable event scope than spot and perpetual contract markets, making permissionless deployment crucial for ecosystem development. To ensure clear market definition and consistent rules, validators will vote to decide on the available outcome market templates, and the template standards will be stored and executed on-chain. Deployers can create markets based on any template and are responsible for defining and settling the markets according to the template. The protocol allows multiple deployers to deploy markets corresponding to the same template.
According to the plan, HIP-4 deployers are required to stake 500,000 HYPE tokens. If the market definition is unclear, the settlement is not done correctly according to the template, or if the market is not settled correctly within one week after the market outcome, validators can vote to confiscate the stake. The deployer's staking period is 6 months, and all market settlements must be completed before unstaking. In the initial stage, each deployer can create 100 outcomes (corresponding to 200 Outcome Tokens), and an auction mechanism will be introduced later to expand the quota.
Furthermore, HIP-4 deployers can set up to a maximum of 50% fee sharing for the deployed markets in the future, and the related fee rate configuration feature will be introduced in subsequent versions. Official standard markets can still be deployed directly by validators, but the expected annual quantity will be limited to fewer than 10. Hyperliquid emphasized that the above design is still a preliminary plan, and adjustments will be made based on community feedback in the future. More details will be announced after permissionless deployment and official documentation updates are released on the testnet.
