Hyperliquid API Announcements

Some info request rate limits will be updated on the next network upgrade to improve overall API stability. The change will happen after Sep 8 at 0:00 UTC. The notable changes are that meta, spotMeta, assetCtxs, openOrders, candleSnapshot are increased to weight 20. See docs for more details: https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/api/rate-limits API users can track these heavier endpoints through websocket streams, and/or less frequent requests. The new limits are already live on testnet, for those who wish to validate their trading. The most common operations for API usage including order placement, order cancel, order status, and clearinghouseState are unaffected.

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

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

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

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

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

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

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

There will be network upgrade around 07:30 UTC. Expect ~5 minutes of downtime.

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

The network upgrade has been rescheduled to 12:00 UTC (1.5 hours later). Apologies for the inconvenience.

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

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

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

Testnet now supports sending spot assets between the L1 and the EVM. Spot assets on the L1 are called “native spot” while ones on the EVM are called “EVM spot”. The spot deployer can link their native spot asset to any ERC20 contract deployed to the EVM. However, in order for transfers between the two to work the system address (0x2222222222222222222222222222222222222222) must have the total non-system balance on the other side. For example, if you want to deploy an ERC20 contract for an existing native spot asset, the system contract should have the entirety of the EVM spot supply equal to the max native spot supply. Once this is done the spot deployer needs to send a spot deploy action to link the token to the EVM: /** @param token - The token index to link @param address - The address of the ERC20 contract on the evm. @param evmExtraWeiDecimals - The difference in Wei decimals between native and EVM spot. E.g. native PURR has 5 weiDecimals but EVM PURR has 18, so this would be 13. EVM wei decimals should be at least native wei decimals. */ interface SetEvmContract { type: “setEvmContract”; token: number; Address: address; evmExtraWeiDecimals: number; } Once a token is linked you can convert between native and EVM spot by sending the token to the system address (0x2222222222222222222222222222222222222222). This can be done on the L1 using a spotSend action (or via the frontend) and on the EVM by using an ERC transfer. There are currently no checks that the system address has sufficient supply or that the contract is a valid ERC20, so be careful when sending funds. EVM PURR has been deployed as 0x8cDE56336E289c028C8f7CF5c20283fF02272182 Below is a sample script for deploying an ERC20 token to the EVM and linking it to a native spot token.

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

The testnet EVM now provides a system contract that allows querying native L1 information. The contract is available at 0x1111111111111111111111111111111111111111 and has methods for querying the L1 block number as well as oracle prices. The L1 block production logic directly updates the system smart contract's values. Therefore, the values are guaranteed to match the L1 state at the time the EVM block is constructed. Attached are the solidity and ABI files for the system contract as well as a python script that calls the contract and prints the results. Happy building. Please share any questions or feedback.

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