Skip to main content

Chain ID

999

Currency

HYPE

Explorer

purrsec.com

​
Endpoints

https://edge.goldsky.com/standard/evm/999?secret=YOUR_SECRET

​
Quick Start

curl "https://edge.goldsky.com/standard/evm/999?secret=YOUR_SECRET" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'

​
Node Types

Edge RPC provides two distinct node pools for HyperEVM, allowing you to choose the right backend for your use case.
Our HyperEVM pool has two node types:
TypeNodeDescriptionUse Case
systx*nanorethFull archive nodes with complete historical state, includes system transactionsHistorical queries, indexing, debugging
standard*hlnodeOptimized for realtime/latest queries, no historical state, excludes system transactionsFrontend dApps, realtime data
If you don’t specify a node type, requests may load-balance among different node types, which can cause inconsistent results when mixing archival and realtime queries.

​
Using Archive Nodes (nanoreth) - Includes System Transactions

For consistent archival data with system transactions (e.g., for indexing), specify use-upstream=systx*: 
https://edge.goldsky.com/standard/evm/999?secret=YOUR_SECRET&use-upstream=systx*

curl "https://edge.goldsky.com/standard/evm/999?secret=YOUR_SECRET&use-upstream=systx*" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"eth_getBlockByNumber","params":["0x1", true],"id":1}'

​
Using Full Nodes (hlnode) - Excludes System Transactions

For realtime queries without system transactions (e.g., for frontend dApps), specify use-upstream=standard*: 
https://edge.goldsky.com/standard/evm/999?secret=YOUR_SECRET&use-upstream=standard*

curl "https://edge.goldsky.com/standard/evm/999?secret=YOUR_SECRET&use-upstream=standard*" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'