Hyperliquid API Announcements

A more mature version of action hashing has been enabled with the most recent network upgrade. The new hashing scheme is more consistent, extensible, and faster to compute. See the python and rust SDKs for full working examples. Note that the previous version of hashing is still accepted on the L1 and its deprecation would come with 1 month of notice. However, as the new hashing is both more efficient and a somewhat bigger change, it is recommended to migrate as soon as possible. Please let the dev team know of any issues during migration. Side note: for those using batch modify actions from a very old version of the python SDK, there is a slight modification that is needed, which is to add a constant to the end of the tuple to be hashed https://github.com/hyperliquid-dex/hyperliquid-python-sdk/blob/0.1.20/hyperliquid/exchange.py#L199 This is the only action that has a breaking change, and only if you are using a very old version. Apologies for the oversight in backward compatibility here.

There will be a network upgrade around 22:00 UTC. Expect 2-5 minutes of downtime.

There will be a network upgrade around 22:00 UTC. Expect 2-5 minutes of downtime.

There will be a network upgrade around 22:00 UTC. Expect 2-5 minutes of downtime.

There will be a network upgrade around 22:00 UTC. Expect 2-5 minutes of downtime.

There will be a network upgrade around 22:00 UTC. Expect 2-5 minutes of downtime.

There will be a network upgrade around 22:30 UTC. Expect 2-5 minutes of downtime.

There will be a network upgrade around 23:30 UTC. Expect 2-5 minutes of downtime.

Update: the network upgrade will be taking place at 23:00 UTC - 30 minutes after the initial scheduled time.

There will be a network upgrade around 22:30 UTC. Expect 2-5 minutes of downtime.

Update: the network upgrade will be taking place at 23:00 UTC - 1 hour after the initial scheduled time.

There will be a network upgrade around 22:00 UTC. Expect 2-5 minutes of downtime. After a network upgrade, orders are post-only for 120 seconds.

There will be a network upgrade around 22:00 UTC. Expect 3-5 minutes of downtime.

This message was originally sent in the Discord server at 23:40 UTC. Apologies for the delay in TG: 1. The downtime from 15:41 to 15:55 UTC today was due to a 30x traffic spike, overwhelming the API servers. The L1 faced no issues but the website and API were mostly unreachable during this time. Adjustments have been made, including increasing the specs on the API servers, adding more redundant API servers, and increasing weights for rate limits for certain heavy API requests. For automated traders, it's recommended to use websockets for most API endpoints whenever available. Apologies for the inconvenience caused. Hyperliquid has been seeing significant growth over the past few days so there will be some growing pains as the platform matures. 2. Beginning tomorrow 22:00 UTC, Coinbase will be removed from the spot oracle sources due to API reliability issues. The oracle set will be Binance, OKX, Kraken, Bybit, and Kucoin spot prices for each asset, with weights 3, 2, 2, 2, 1.

Please note that the legacy USDC.e bridge will be sunset over the next week, as the migration to the native USDC bridge is almost complete. If you have any unclaimed USDC.e withdrawals (withdrawn from L1 but not claimed on Arbitrum), you should claim those. You should start routing requests to the new bridge contract here https://arbiscan.io/address/0x2df1c51e09aecf9cacb7bc98cb1742757f163df7 To deposit, simply send native USDC to the new bridge To withdraw, send a bridge2 withdrawal L1 request. See the python SDK for an example via API. The withdrawal fee is 2 USDC on the L1 but costs no Arbitrum gas. Important: Withdrawals now have a delay of 200 seconds for security purposes. Though inconvenient, this greatly enhances bridge security. See the contract code and audit report for more details.

There will be a network upgrade around 22:00 UTC. Expect 2-5 minutes of downtime

The Hyperliquid network experienced downtime from 23:35-23:52 UTC due to a safety check that triggered in the matching engine logic, causing the nodes to halt instead of propagating incorrect state. This was an edge case that has been patched, and there will be a network upgrade at 1:00 UTC (around 25 minutes from now) to solidify the fix and reenable deposits to HLP. Expect around 2-5 minutes of downtime.

The set of spot oracle sources will be expanded to include Coinbase and Kucoin on the next network upgrade. The updated constituents will be Binance, OKX, Kraken, Bybit, Coinbase, Kucoin, with weights 3, 2, 2, 2, 2, 1 respectively. This change will not happen for at least 24 hours. The resulting index price change will be minor in most cases, but will be more robust during extreme volatility.

There will be a network upgrade around 22:00 UTC. Expect 2-5 minutes of downtime. Happy new year!

There will be a network upgrade around 22:30 UTC. Expect 2-5 minutes of downtime.