Hyperliquid has rolled out its HIP-4 feature update, allowing deployers to adjust the ratio of outcome fees to configuration fees, with the mainnet launch set to follow a conservative phased approach.

Hyperliquid announces HIP-4 has rolled out multiple new features: Deployers can now add named results after a question is created, with the new results’ initial balances matching the pending fallback balance; Template instantiation now requires setting a deployerFeeScale — a fee multiplier similar to HIP-3, which deployers can configure between 0 and 10 to charge result fees; A new shortString type hint has been added for template-side names, simplifying interface field parsing; Settlement details have been pruned from L1 state, so dependent node APIs or precompiled application readers can index required data independently; Multiple new template sets have been added to the testnet, with template IDs using sequential suffixes — all except the highest sequential ID in each set are marked as deprecated templates. After the next network upgrade, the fee mechanism will activate for validator-deployed result markets, with the average transaction fee for these markets set at half the rate of non-result spot trades. The HIP-4 mainnet launch will follow a conservative phased rollout: Each deployer will initially be capped at 100 concurrent results and a maximum of 500 result deployments per day; Once the technology stabilizes, these limits are expected to quickly rise to 1000 concurrent results and 5000 daily deployments, with further limit increase plans to be developed based on feedback.