Overview

HypeRPC provides high-performance JSON-RPC endpoints for the Hyperliquid EVM L1. Every endpoint is a smart proxy that sits in front of two node backends, automatically routing each request to the most appropriate one.

Architecture

Each endpoint is powered by two complementary backends:

Nanoreth

Reth-based archive node. Full EVM compatibility, historical data from genesis, and trace call support.

HLNode

Official Hyperliquid node binary. Lowest latency for real-time queries with direct network connectivity.

How Routing Works

When a request arrives, the proxy evaluates the method and routes it automatically:

• Archive/trace methods (e.g. debug_traceTransaction) are routed to Nanoreth.

• Standard methods (e.g. eth_blockNumber) are routed to the fastest available upstream.

• Explicit selection — use the use-upstream query parameter to force a specific backend.

Protocols

Every endpoint supports both HTTPS and WSS out of the box:

HTTPS

Standard request/response for all JSON-RPC methods. Ideal for queries, contract calls, and batch requests.

WSS

Persistent WebSocket connections for real-time subscriptions like eth_subscribe.

Quick Example

Get Latest Block Number

curl -X POST <URL> \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'

curl -X POST <URL> \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'

curl -X POST <URL> \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'

Fine-tune your requests with query parameters to select a specific upstream or bypass caching.