Hyperliquid API Announcements

The first pass of the Hyperliquid EVM is live on testnet. It would be great to get initial dev feedback. Please note that it is a rough MVP, testnet only, and may be reset without warning to fix issues that arise. There are some big features that are not yet done, including: 1. EVM block explorer 2. JSON-RPC queries with non-latest block number 3. Integration with other L1 state The JSON-RPC endpoint is

https://api.hyperliquid-testnet.xyz/evm

. The chain ID is 998. Users can use the native token faucet:

curl -X POST --header "Content-Type: application/json" --data '{"type":"ethFaucet", "user": "..."}' https://api.hyperliquid-testnet.xyz/info

Note that there are currently no official frontend components of the EVM. Users can build their own frontends or port over existing EVM applications. All interaction with the EVM happens through the JSON-RPC. For example, users can add the chain to their wallets by entering the RPC URL and chain ID.

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

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

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

New versions of user signed actions (actions that an API wallet cannot perform) have been released. These include approveAgent, usdSend, spotSend, and withdraw3 . The gitbook docs along with the python and rust sdk's have been updated. The previous versions (connect, connect2, usdTransfer, spotTransfer, and withdraw2) are deprecated and will no longer be supported on testnet in a coming deploy. Support on mainnet will be discontinued after June 9 at 6:00 UTC. If you are using the sdk's, make sure to update to version 0.4.0 before then.

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

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

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

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

Note that JSON object responses returned from the API are not guaranteed to have the same ordering of keys in between network upgrades. E.g. an endpoint returning {"a": 1, "b": 2} may return {"b": 2, "a": 1} after a network upgrade without being considered a breaking change. This is consistent with the JSON specification, and most languages make it difficult to rely on the ordering of object fields.

On the next network upgrade, info requests sent through websocket will return adjacently tagged responses. Currently the responses are internally tagged, which prevents some response variants from being properly returned. See the docs for examples. Only a handful of info requests are being sent on the websocket at all, and this change will likely only affect 1 or 2 API users. In particular, websocket order entry and HTTP are not affected.

Following up on this, testnet now has legacy signing deprecated. API traders who are unsure which version they are using can try their trading on testnet to confirm. As a reminder, legacy signing will be deprecated on mainnet on May 12 at 6:00 UTC.

Following up on this announcement, legacy signing will be deprecated on May 12 at 6:00 UTC. The current signing method uses MessagePack for more consistent hashing spec and is stricter on nonce checks. See the docs or SDK implementations for more details. Note that if you are using the python or rust SDKs, there is no action item as long as you have updated to a relatively recent version.

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

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

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

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

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

Legacy signing will be deprecated at some point after 0:00 UTC on May 11. The current signing method uses MessagePack for more consistent hashing spec and is stricter on nonce checks. See the docs or SDK implementations for more details. The one month heads up is to give people ample time to migrate. Many users have successfully migrated already, so feel free to ask questions in the api-traders channel in Discord. Note that if you are using the python or rust SDKs, there is no action item as long as you have updated to a relatively recent version.

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