Hyperliquid (HyperEVM) RPC Nodes & Endpoints

Hyperliquid (HyperEVM) public RPC endpoints

Free, third-party public endpoints for reads and prototyping. They are shared and rate-limited, not run by BLAZED.sh, so use a dedicated node for production traffic.

import { JsonRpcProvider } from "ethers";

const provider = new JsonRpcProvider("https://rpc.hyperliquid.xyz/evm");
const blockNumber = await provider.getBlockNumber();
console.log("Hyperliquid (HyperEVM) block:", blockNumber);

Dedicated Hyperliquid (HyperEVM) RPC node vs shared endpoints

HyperEVM exists in the orbit of a perps exchange, so its RPC traffic looks like trading: market makers polling positions and funding, liquidation bots re-checking accounts every block, dashboards streaming fills. That read loop runs continuously, and on a shared endpoint it competes with every other bot running the same loop. The result is jitter, and jitter in a market-making loop is money.

A dedicated HyperEVM RPC node gives the loop a floor: consistent read latency, no shared quota deciding when your liquidation check runs, and throughput for the analytics that funding and liquidation tracking require. On BLAZED.sh the strategy itself runs in a container on the node host, reading over a local socket instead of the public internet.

Hyperliquid (HyperEVM) RPC latency: architecture over benchmarks

Trading on Hyperliquid is a latency sport by design, and the RPC path is the part of the stack you can actually control. A remote gateway adds tens to low hundreds of milliseconds of public-internet round trip per call; a co-located container adds almost nothing. On our live Ethereum product, that architecture delivers sub-10ms calls over a local socket, and dedicated HyperEVM nodes will run the same way.

What a dedicated Hyperliquid (HyperEVM) node costs

BLAZED.sh prices node access in per-request credits granted monthly by your subscription, with a deliberately narrow weight spread: most RPC methods cost 1 credit, a few heavy operations like txpool_content and the trace_replay methods cost 4, and responses over 100KB add 50 credits per MB. The Beta plan is €75 per month with 1M credits, 1 container and 2 scripts; Beta XL is €249 per month with 5M credits, 3 containers and 4 scripts; Enterprise plans add private nodes and archive access. These are the live Ethereum plans today, and pricing is still being finalized. Dedicated Hyperliquid (HyperEVM) nodes will launch on the same credit model, with the waitlist above deciding rollout priority.

Market-making read loops are single-credit calls, so the cost of running a strategy around the clock is a straightforward multiplication rather than a method-weighted estimate.

Perfect for

What is Hyperliquid (HyperEVM)?

Hyperliquid pairs a purpose-built, on-chain order book (HyperCore) with HyperEVM, an EVM environment that lets developers deploy standard Solidity contracts that can interact with the exchange state. HyperEVM uses chain ID 999 and HYPE for gas, so EVM tooling connects normally, while the order-book side is accessed through Hyperliquid's own APIs. The platform's reason for existing is high-frequency perps trading, which means market makers and bots treat every millisecond of RPC and submission latency as edge. As HyperEVM's contract ecosystem grows, indexers and dashboards tracking positions, funding, and liquidations need consistent RPC throughput, the classic case for a dedicated, co-located node rather than a shared public endpoint.

Hyperliquid (HyperEVM) RPC: frequently asked questions