Hyperliquid has released HIP-4 Feature Update: Deployers Can Supplement Results with Configuration Fee Ratio, Mainnet Launch to Follow Conservative Staged Specification

August 14th, Hyperliquid announced that HIP-4 has implemented several new features: Deployers can now add named outcomes after issue creation, and the initial balance of added outcomes will match the pending backstop balance; Template instantiation now requires setting deployerFeeScale—a fee multiplier similar to HIP-3, where deployers can configure between 0 and 10 to charge for outcome fees; Added shortString type hint for template-side names to facilitate interface parsing of fields; Settlement details have been pruned from the L1 state, relying on node APIs or reading precompiled apps to index the required data independently; The testnet has added multiple sets of templates, with template IDs suffixed by a sequence number, considering all templates deprecated except for the maximum number in each set.

After the next network upgrade, the fee mechanism will be enabled for validators' deployed outcome markets, with the average transaction fee in the outcome market being half of the non-outcome spot trading fee. The HIP-4 mainnet launch will follow a conservative phased approach: Each deployer will initially be limited to 100 concurrent outcomes and a maximum of 500 outcome deployments per day; Once technical stability is achieved, the deployer limit is expected to rapidly increase to 1000 concurrent outcomes and 5000 daily deployments, with further limit increase proposals based on feedback.