Hyperliquid HyperEVM RPC
Standard Ethereum JSON-RPC against HyperEVM, the smart-contract layer of Hyperliquid, with WebSocket subscriptions from the same node.
- Standard Ethereum JSON-RPC methods
- eth_subscribe: newHeads · logs · pending
- Archive access for historical state
- debug_* and trace_* on request
- Shared or single-tenant deployment
- Interface
- Ethereum JSON-RPC over HTTP and WebSocket
- Layer
- HyperEVM - the EVM execution layer of Hyperliquid
- Namespaces
- eth · net · web3, with debug and trace on request
- Archive
- available
- Auth
- token, provisioned per subscription
- Rate limits
- quoted per subscription
- Free trial
- up to 24h, no card
What is the difference between HyperEVM and HyperCore?
They are two halves of the same chain. HyperCore is the exchange - order books, perpetuals, fills, liquidations - and it is not an EVM. HyperEVM is the general-purpose smart-contract layer, and it speaks the same JSON-RPC every Ethereum tool already knows. This product is the HyperEVM side.
Does the RPC give me order-book data?
No, and that is the most common mix-up on this chain. Order books and fills live on HyperCore, not on HyperEVM, so no JSON-RPC method returns them. For live order-book data use Hyperliquid WebSocket Streaming, and for history use the Hyperliquid Historical Data Indexer.
Do my existing Ethereum tools work?
Yes. HyperEVM implements the standard JSON-RPC surface, so ethers, viem, web3.py, Foundry and Hardhat work after swapping the endpoint URL. Tracing namespaces are available on request rather than by default, because they are expensive to serve.
How is the HyperEVM RPC priced and provisioned?
It is not on sale yet - HyperEVM RPC is in build, so there is no tier to buy today and no price to quote. Tell us on Telegram what throughput and archive depth you need and we come back to you first when it opens. A dedicated node is the way onto HyperEVM today. Billing, when it opens, is the same as everything else here: crypto-only, monthly and prepaid.
Get Hyperliquid HyperEVM RPC.
Set up over Telegram with an engineer — endpoint, token, tuning.