HyperLiquid is a Layer 1 blockchain that provides Ethereum Virtual Machine (EVM) compatibility. It operates on a custom consensus mechanism and allows deployment of Ethereum smart contracts.
QuickNode's HyperLiquid Service
QuickNode provides infrastructure access to HyperLiquid through a dual-path routing system:
/evm
Path - Routes to HyperEVM nodes for standard Ethereum JSON-RPC methods including account balances, blocks, transactions, smart contract calls, and transaction broadcasting.
/nanoreth
Path - Routes to specialized nodes that provide transaction tracing and debugging. Supports trace methods that capture internal contract calls, gas usage, and state changes during execution.
How to Use Different Routes
Here are basic examples to get you started with each endpoint. Add /evm
to your endpoint URL for standard blockchain operations and /nanoreth
when you need transaction tracing.
Standard blockchain query:
curl https://docs-demo.hype-mainnet.quiknode.pro/evm \
-X POST \
-H "Content-Type: application/json" \
--data '{"method":"eth_getBlockByNumber","params":["latest",false],"id":1,"jsonrpc":"2.0"}'
Transaction trace analysis:
curl https://docs-demo.hype-mainnet.quiknode.pro/nanoreth \
-X POST \
-H "Content-Type: application/json" \
--data '{"method":"debug_traceBlockByNumber","params":["0xbdd86d"],"id":1,"jsonrpc":"2.0"}'
Please make sure to append /evm
to your endpoint URL for standard blockchain operations and /nanoreth
when you need transaction tracing.
Method Compatibility
The following table shows which methods are supported on each endpoint and provides recommendations for optimal performance:
Method Category | Method Name | /evm | /nanoreth | Recommended |
---|---|---|---|---|
Standard Queries | eth_getBlockByNumber | ✅ Optimized | ✅ Available | /evm |
eth_getBalance | ✅ Optimized | ✅ Available | /evm | |
eth_getTransactionByHash | ✅ Optimized | ✅ Available | /evm | |
Transaction Ops | eth_sendRawTransaction | ✅ Optimized | ✅ Available | /evm |
eth_call | ✅ Fast (latest only) | ✅ All blocks | /nanoreth for historical data | |
Debug API | debug_getBadBlocks | ❌ | ✅ Only | /nanoreth |
debug_storageRangeAt | ❌ | ✅ Only | /nanoreth | |
debug_traceBlock | ❌ | ✅ Only | /nanoreth | |
debug_traceBlockByHash | ❌ | ✅ Only | /nanoreth | |
debug_traceBlockByNumber | ❌ | ✅ Only | /nanoreth | |
debug_traceTransaction | ❌ | ✅ Only | /nanoreth | |
Trace API | trace_block | ❌ | ✅ Only | /nanoreth |
trace_filter | ❌ | ✅ Only | /nanoreth | |
trace_rawTransaction | ❌ | ✅ Only | /nanoreth | |
trace_replayBlockTransactions | ❌ | ✅ Only | /nanoreth | |
trace_replayTransaction | ❌ | ✅ Only | /nanoreth | |
trace_transaction | ❌ | ✅ Only | /nanoreth |
- Trace methods like
debug_traceTransaction
andtrace_transaction
only work on/nanoreth
endpoint - Historical queries for
eth_call
method require/nanoreth
-/evm
only supportslatest
block - Rate limits are lower on
/nanoreth
due to the computational overhead of trace operations - Timeouts should be set appropriately for complex trace operations to prevent request failures
Key Implementation Differences
The /evm
and /nanoreth
endpoints handle HyperLiquid's internal system operations differently, resulting in data variations that developers need to account for in their applications.
Extra System Transactions on /nanoreth
:
/nanoreth
includes system transactions in block queries (eth_getBlockByNumber
,eth_getBlockByHash
) that are not present in/evm
responses. These transactions handle token transfers between HyperCore and HyperEVM layers.- System transactions can be identified by their
gasPrice: 0
value. - Filter requirement: Exclude transactions where
gasPrice === 0
when displaying user transactions.
Extra Events on /nanoreth
:
/nanoreth
includes additional ERC20 transfer events from HyperCore bridging operations ineth_getLogs
responses and WebSocket subscriptions.
Transaction Hash Lookups:
- System transaction hashes return "transaction not found" on
/evm
endpoint. Useeth_getSystemTxsByBlockHash
andeth_getSystemTxsByBlockNumber
methods to access system transactions on/evm
.
Support & Resources
For technical support, visit QuickNode Support. For HyperLiquid protocol details, see the official documentation.