Hyperliquid Narrows Impact Scope of Operation Deprioritization Rule, Activation Delayed by Another Mainnet Upgrade

October 28: According to Hyperliquid's API announcements channel, the team has adjusted its operation deprioritization rules based on user feedback: deprioritization for operations other than noop, scheduledCancel, cancel, cancelByCloid, order, modify, and batchModify will affect only the main account and the subaccounts or vaults involved in that operation, rather than all subaccounts and vaults. The rule will now take effect one mainnet upgrade later, allowing time for feedback and user adjustments. In addition, after the next network upgrade, HyperEVM error responses will include the specific L1 (layer-1) error instead of uniformly returning error code 10055.