Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.chainstack.com/llms.txt

Use this file to discover all available pages before exploring further.

Every Chainstack Hyperliquid node exposes two HyperEVM JSON-RPC paths on the same endpoint:
Console labelPathWhat it returns
JSON-RPC API (default)/evmhl-node-compliant output; system transactions stripped from block-shaped responses
JSON-RPC API (with system tx)/nanorethFull nanoreth output; system transactions included in blocks and receipts
You don’t pick one at deploy time — both are always available. Append the path you need to your endpoint URL.

​
What system transactions are

System transactions are protocol-generated pseudo-transactions that record HyperCore state changes on the HyperEVM ledger. They have no signing key — the protocol creates them to bridge state between HyperCore and HyperEVM (HYPE deposits and withdrawals, spot token transfers, and similar). They always carry gasPrice: 0x0 and originate from system addresses:
  • 0x2222222222222222222222222222222222222222 — HYPE native token bridge
  • 0x20000000000000000000000000000000000000XX — per-token bridge contract, where XX is the big-endian token index (token 200 → …00c8)
For background, see Hyperliquid docs: HyperCore ↔ HyperEVM transfers and the nanoreth README.

​
How /evm and /nanoreth differ in practice

Behavior verified against block 0x202e371 (one HYPE bridge system tx). All methods are present on both paths; the difference is whether system transactions appear in the response:
Method/evm/nanoreth
eth_getBlockByNumber / eth_getBlockByHashtransactions array excludes system txtransactions array includes system tx
eth_getBlockTransactionCountByNumber / ByHashcount excludes system txcount includes system tx
eth_getBlockReceiptsreceipts array excludes system tx receiptreceipts array includes system tx receipt
eth_getTransactionReceipt for a system tx hashreturns nullreturns the receipt
eth_getTransactionByHash for a system tx hashreturns the transactionreturns the transaction
eth_getSystemTxsByBlockNumber / ByHashreturns system txsreturns system txs
debug_* / trace_* / ots_* methodsunchangedunchanged
All non-system-tx methods (regular blocks, txs, receipts, traces)unchangedunchanged
In short: /evm only hides system transactions inside block-shaped responses — the transactions array, the transaction count, the receipts array, and eth_getTransactionReceipt keyed by a system tx hash. Everything else, including direct system tx lookup by hash via eth_getTransactionByHash and the dedicated eth_getSystemTxsBy* methods, behaves identically on both paths.

​
Endpoint format

# JSON-RPC API (default), hl-node-compliant
https://hyperliquid-mainnet.core.chainstack.com/<auth>/evm

# JSON-RPC API (with system tx), nanoreth full output
https://hyperliquid-mainnet.core.chainstack.com/<auth>/nanoreth

# WebSocket (HyperEVM)
wss://hyperliquid-mainnet.core.chainstack.com/<auth>/evm

# Info HTTP API (HyperCore)
https://hyperliquid-mainnet.core.chainstack.com/<auth>/info
Find both paths in the console under Access and credentials on any Hyperliquid node. Username/password access is provided alongside.
Last modified on April 29, 2026