HyperEVM is the EVM chain that runs alongside Hyperliquid's order book. Like any EVM chain, you reach it through a JSON-RPC endpoint: a wallet, Foundry, viem, ethers or an indexer all speak the same protocol.
Hyperliquid runs a public endpoint that anyone can use without signing up. This guide lists the URLs, what the public endpoint allows, where it stops, and how to get archive access when you need more.
The short answer
| Network | Chain ID | Public endpoint | On a Hypedexer key |
|---|---|---|---|
| HyperEVM mainnet | 999 | https://rpc.hyperliquid.xyz/evm | https://rpc.hypedexer.com/hyperevm/$KEY |
| HyperEVM testnet | 998 | https://rpc.hyperliquid-testnet.xyz/evm | https://rpc.hypedexer.com/hyperevm-testnet/$KEY |
| Elysium mainnet | 99901 | https://rpc.hypedexer.com/elysium/$KEY | |
| Elysium testnet | 99801 | https://rpc.hypedexer.com/elysium-testnet/$KEY |
The public URLs and chain IDs are the ones in Hyperliquid's HyperEVM documentation. On a Hypedexer key, the same URLs answer over WebSocket with wss:// instead of https://.
Adding HyperEVM to a wallet
In MetaMask or any EVM wallet, add a network by hand:
- Network name: HyperEVM
- RPC URL:
https://rpc.hyperliquid.xyz/evm, or your ownhttps://rpc.hypedexer.com/hyperevm/$KEY - Chain ID: 999
- Currency symbol: HYPE
HYPE on HyperEVM has 18 decimals, on mainnet and testnet alike. A wallet cannot set a header, which is why the Hypedexer key goes in the path: the URL works as pasted.
What the public endpoint allows
The public endpoint is the right place to start, and for a wallet or a light script it is often all you need. Its limits, from Hyperliquid's own documentation:
- 100 requests a minute per IP for
rpc.hyperliquid.xyz/evm(rate limits). - Latest block only for
eth_call,eth_estimateGas,eth_getBalance,eth_getCode,eth_getStorageAtandeth_getTransactionCount. Requests that need historical state are not supported on the default implementation (JSON-RPC). eth_getLogsover 50 blocks at most per query, with up to 4 topics.- No WebSocket: there is no WebSocket JSON-RPC on the public endpoint, so no
eth_subscribe.
None of this is a flaw. A shared endpoint has to be fair to everyone, and Hyperliquid's documentation itself points to other providers for archive functionality.
When you need more
You outgrow the public endpoint the day one of these becomes part of the job:
- Reading the past. A balance, a contract's storage or the result of an
eth_callat a block that is not the latest one: an accounting snapshot, a backtest, a dispute over what a vault held on a given day. - Indexing events. Fifty blocks per
eth_getLogsmeans thousands of calls to walk a contract's history, each one counted against 100 a minute. - Following the chain live. New blocks and logs pushed over
eth_subscribeinstead of polling. - Steady volume. A bot or a backend that cannot share a per-IP budget with everyone behind the same address.
Archive RPC on a Hypedexer key
Hypedexer serves HyperEVM and Elysium JSON-RPC from archive nodes run by Enigma, a Hyperliquid validator. Every block's state is queryable, over HTTPS and WebSocket.
| Public endpoint | Free key | Paid plans | |
|---|---|---|---|
| Requests | 100 a minute, per IP | 10 a second | up to 300 a second |
| State | latest block only | any block, archive | any block, archive |
eth_getLogs range | 50 blocks | 2,000 blocks | up to 100,000 blocks |
| WebSocket | none | eth_subscribe | eth_subscribe |
Every plan carries a monthly quota of RPC requests:
- Free: 1M requests a month, no card.
- RPC plan: 15M requests a month for $49, at 50 requests a second. JSON-RPC only, no Data API.
- Data API plans: Starter includes 25M, Growth 150M, Scale 500M, on top of the API credits.
Most calls count as one request. eth_getLogs, eth_getFilterLogs and eth_getBlockReceipts count three, Otterscan's ots_* two, and eth_chainId nothing. Each response reports what it counted, so usage is never a surprise at the end of the month. Full plans are on pricing, and the methods, limits and errors in the RPC docs.
Calls to copy
The latest block:
curl https://rpc.hypedexer.com/hyperevm/$HYPEDEXER_KEY \
-H 'content-type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber","params":[]}'A balance at a past block, which the public endpoint refuses:
curl https://rpc.hypedexer.com/hyperevm/$HYPEDEXER_KEY \
-H 'content-type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"eth_getBalance","params":["0xYourAddress","0x1000000"]}'With Foundry, the URL goes straight into --rpc-url:
cast block-number --rpc-url https://rpc.hypedexer.com/hyperevm/$HYPEDEXER_KEY
cast balance 0xYourAddress --block 16777216 --rpc-url https://rpc.hypedexer.com/hyperevm/$HYPEDEXER_KEYAnd new blocks pushed over WebSocket:
{"jsonrpc":"2.0","id":1,"method":"eth_subscribe","params":["newHeads"]}sent on wss://rpc.hypedexer.com/hyperevm/$HYPEDEXER_KEY.
FAQ
What is the HyperEVM chain ID? 999 on mainnet, 998 on testnet.
What is the HyperEVM RPC URL? https://rpc.hyperliquid.xyz/evm is Hyperliquid's public endpoint. With a Hypedexer key, https://rpc.hypedexer.com/hyperevm/$KEY.
Is there a free HyperEVM RPC? Yes: Hyperliquid's public endpoint, at 100 requests a minute per IP and latest-block state. A free Hypedexer key gives 1M requests a month on archive nodes, with no card.
Does the HyperEVM RPC support WebSocket? Not the public endpoint. On a Hypedexer key, every plan serves WebSocket with eth_subscribe.
How do I query HyperEVM state at a past block? You need an archive node: the public endpoint answers state calls for the latest block only. Any Hypedexer key serves every block.
Does it also serve Hyperliquid's order book data? No: HyperEVM RPC is the EVM chain. Fills, the order book, funding and liquidations from HyperCore come from the Data API, on the same key.