Skip to main content
hypernode’s EVM RPC is a dedicated endpoint for HyperEVM queries and transaction submission. No shared public endpoint, no rate limit contention with other users.
This endpoint serves HyperEVM (chain ID 999), not HyperCore. HyperCore orders, fills, and the L1 matching engine are served by the WebSocket stream and REST API. The EVM RPC is for smart contract reads, token balances, and HyperEVM transaction submission.

​
Endpoint

Standard Ethereum JSON-RPC 2.0 format. Requires API key via x-api-key header.

​
Supported methods

​
What this is

This is a dedicated RPC. Your requests go to your own capacity, not a shared public endpoint. One hypernode API key gives you HyperCore trading, the EVM RPC, the WebSocket stream, and the L4 order book. Combined with the HyperCore trading API, one hypernode key gives you both chains: place orders on HyperCore via POST /v2/order, read contracts and submit transactions on HyperEVM via POST /v2/evm.

​
Limitations

Recent blocks only. Block and state queries work for the last ~300 blocks. Older blocks return an error. For deep historical state queries, use an archival provider. No WebSocket subscriptions. eth_subscribe, eth_newFilter, and eth_newBlockFilter are not supported. Poll eth_blockNumber or eth_getLogs instead. No debug/trace. debug_traceTransaction and trace methods are not available. No mempool via RPC. eth_pendingTransactions and txpool_content are not supported on HyperLiquid’s RPC. However, hypernode streams pre-block EVM transactions via the WebSocket as evmRawTx events. Subscribe with {"action": "subscribe", "filters": {"action_types": ["evmRawTx"]}} to see every HyperEVM transaction before it is included in a block. See Event Types for details.

​
Use cases

  • Read HyperEVM contract state (token balances, LP positions, protocol data)
  • Submit signed HyperEVM transactions via eth_sendRawTransaction
  • Monitor recent EVM blocks and transaction receipts
  • Query event logs from HyperEVM smart contracts