Hyperliquid Narrows Priority Rule, Delaying Start Until Another Mainnet Upgrade

In an Oct. 28 update, Hyperliquid narrowed the reach of a planned operation-priority rule and delayed its start until after another mainnet upgrade, giving users more time to respond to the change.

The revised scope applies to operations other than noop, scheduledCancel, cancel, cancelByCloid, order, modify and batchModify. For operations covered by the change, a priority downgrade will affect the master account and only the subaccounts or vaults involved in that operation. The downgrade’s effects will no longer extend across every subaccount and vault tied to the master account.

Hyperliquid said the added delay will give users time to provide feedback and adjust their systems. The platform has also revised testnet operation-priority rules in a separate update.

A separate update will change HyperEVM error responses after the next network upgrade. Responses will include the specific Layer 1 error instead of uniformly returning code 10055.