Телеграм канал «Hyperliquid API Announcements»

On the next network upgrade:
1. The number of gossip priority slots will increase from 2 to 3.
2. The write priority fee changes from described above will be activated.

These changes are live on testnet. Any feedback is appreciated.

There will be a network upgrade around 9:30 UTC. Expect ~10 minutes of downtime.

Based on user feedback to the testnet improvements shared previously:

1. noop and scheduledCancel actions will not affect the prioritization of other actions under the new priority system. Specifically, actions other than noop, scheduledCancel, cancel, cancelByCloid, order, modify, batchModify cause all actions to be deprioritized while that action has not yet been committed.
2. cDeposit2 has been added, which is like cDeposit but can be agent-signed. See https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/api/exchange-endpoint#deposit-into-staking-agent for details.

Based on user feedback: On the next network upgrade, HIP-3 volume's contribution toward L1 user rate limits will be scaled by the total fee, instead of the protocol portion of the fee. Most HIP-3 perps will see a 2x increase in volume contribution toward rate limits.

This is not a breaking change as it is strictly beneficial for users. This change does not affect fee tier volume contributions.

Based on user feedback, the following improvements will be made to write priority fees. These changes are on live on testnet already and only affect latency-sensitive users. As a reminder, both read and write priority fees are in scope for the bug bounty program, like all features live on mainnet. Several users have responsibly disclosed edge cases and received bounties, for example by identifying ways ALO prioritization could be obtained for non-ALO orders.

1. Mempool prioritization will only work for users in Standard abstraction. As a reminder, latency sensitive users should not use abstractions such as Unified Account and Portfolio Margin.
2. Actions other than cancels, orders, and modifies sent on HyperCore will cause all actions to be deprioritized while that action has not yet been committed. This holds across subaccounts associated with and vaults led by the same master user.
3. Users who have ever directly sent CoreWriter actions will be deprioritized in the mempool. This does not affect the vast majority of use cases of CoreWriter, which go through smart contracts rather than the user itself.
4. IOC and ALO priority fees require a minimum delegatable balance of 10 HYPE. The priority fee charged remains a function of only the executed size.

As always, feedback is appreciated.

There will be a network upgrade around 8:15 UTC. Expect ~10 minutes of downtime.

For node operators running hl-visor: It is important to update to the latest version within the next week. After that, there will be a breaking change where hl-visor will no longer be compatible with future versions of hl-node.