Digital Currency

Add as a preferred source on Google

Hyperliquid Limits Downgrade Reach, Sets Activation After Further Mainnet Upgrade

Seven operation types are exempt. HyperEVM error replies are expected to identify specific Layer 1 errors after the next network upgrade.

Updated 1 min read
A trader adjusts account settings at a laptop in a Singapore shared workspace. / TokenPost.ai
A trader adjusts account settings at a laptop in a Singapore shared workspace. / TokenPost.ai

A planned Hyperliquid priority downgrade will apply only to accounts involved in covered operations, while seven operation types remain exempt.

In an Oct. 28 update, Hyperliquid’s API announcements channel listed seven operation types outside the rule: noop, scheduledCancel, cancel, cancelByCloid, order, modify and batchModify. Other operations remain covered.

Under the earlier approach, a priority reduction could extend to every subaccount and vault connected to a master account. The revised scope limits the effect to the master account and the associated subaccounts or vaults taking part in the specific operation.

Hyperliquid said the delay followed user feedback and gives users additional time to adjust their systems and comment. The rule will take effect after one more mainnet upgrade; the channel did not give a calendar date. It also said the narrower scope should be easier for automated traders to work around.

Separately, after the next network upgrade, HyperEVM responses are expected to return specific Layer 1 errors instead of the general code 10055.

Related articles

View all