You don’t pick one at deploy time and there’s nothing to enable — both paths exist by default on every node. 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 carrygasPrice: 0x0 and originate from system addresses:
0x2222222222222222222222222222222222222222— HYPE native token bridge0x20000000000000000000000000000000000000XX— per-token bridge contract, whereXXis the big-endian token index (token 200 →…00c8)
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:
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
hyperliquid-testnet.core.chainstack.com with the same /evm and /nanoreth paths.
Find both paths in the console under Access and credentials on any Hyperliquid node, mainnet or testnet. Username/password access is provided alongside.
Related resources
- Hyperliquid methods — full method-by-method availability and which path each runs on
- Hyperliquid infrastructure FAQ — node types, rate limits, and the dual-layer architecture
eth_getSystemTxsByBlockNumber— dedicated method for system transactionseth_getSystemTxsByBlockHash— same, keyed by block hash- Build better with Hyperliquid — Chainstack’s Hyperliquid RPC overview