BlockReq
Edit on GitHub

HyperEVM API

HyperEVM endpoints use the EVM JSON-RPC Core API over HTTPS only. WebSocket (WSS) is not yet available for HyperEVM.

Endpoint

ItemValue
NetworkHyperEVM Mainnet
ProtocolEVM JSON-RPC 2.0
Chain ID999 (0x3e7)
Public HTTPShttps://hyperevm-rpc.blockreq.com/v1/rpc/public
Private HTTPShttps://hyperevm-rpc.blockreq.com/v1/rpc/BRQ1P0000000000000000000000000000000000000000000000000000000

These URLs use the product path /v1/rpc plus /public or BRQ1P0000000000000000000000000000000000000000000000000000000. Callers use BlockReq HTTP on this host; there is no WSS URL for HyperEVM yet, so eth_subscribe is not available.

Core Methods

HyperEVM uses the shared EVM JSON-RPC Methods catalog.

HyperEVM Behavior

  • Block history: full chain history is available on the same URL, so blocks and state at past blocks can be queried. Recent blocks come from BlockReq's own HyperEVM node; older blocks and state are served through other HyperEVM providers.
  • System transactions: responses leave out HyperCore system transactions, the same as the official Hyperliquid node RPC.
  • Read precompiles: eth_call to the HyperCore read precompiles is supported only at the latest block.

BlockReq does not currently document or guarantee eth_getProof, debug_*, or trace_* on HyperEVM.