Quicknode's Hyperliquid Service

Quicknode provides infrastructure access to Hyperliquid's two-layer architecture: HyperEVM (execution layer) and HyperCore (exchange layer). Each component serves different purposes and provides specialized endpoints.

HyperEVM Service

HyperEVM is Hyperliquid's execution layer that provides standard Ethereum JSON-RPC compatibility for smart contracts, account queries, and transaction operations. Access HyperEVM 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. 该 /evm endpoint retains only recent block data (older data is periodically pruned). It is not suitable for historical queries.

/nanoreth Path - Routes to specialized nodes that provide transaction tracing and debugging, with a full historical archive. Supports trace methods that capture internal contract calls, gas usage, and state changes during execution.

HTTP 端点

Quicknode's HTTP endpoints provide JSON-RPC API access with multiple performance tiers designed for different application requirements.

https://your-endpoint.quiknode.pro/auth-token/evm
https://your-endpoint.quiknode.pro/auth-token/nanoreth

Best for: Building Web3 applications that interact with HyperEVM's smart contracts and blockchain data. Use these endpoints for deploying contracts, querying account balances and transaction history, calling smart contract functions, broadcasting transactions, and performing blockchain data analysis in development or production environments.

WebSocket (WSS) 端点

Quicknode's WebSocket endpoints provide real-time blockchain data streaming through persistent connections.

wss://your-endpoint.quiknode.pro/auth-token/nanoreth

Best for: DeFi applications and analytics platforms that need real-time blockchain updates. Use WebSocket connections to monitor new blocks as they're produced, track transaction confirmations, listen for smart contract events, update price feeds instantly, and build responsive block explorers or portfolio dashboards.

WebSocket Support

关于 Hyperliquid HyperEVM Service, WebSocket functionality is supported only on the /nanoreth namespace. The /evm 命名空间 does not support WebSockets at this time.

WebSocket Limits: WebSocket responses are capped at a predefined limit, which may change over time. For large responses, it is recommended to use a POST request instead. If the response size exceeds the limit, the returned error code will be -32616.

How to Use HyperEVM 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"}'

WebSocket subscription (real-time new blocks):

const WebSocket = require('ws');

const ws = new WebSocket('wss://your-endpoint.quiknode.pro/your-token/nanoreth');

ws.on('open', () => {
  // Subscribe to new block headers
  ws.send(JSON.stringify({
    "jsonrpc": "2.0",
    "id": 1,
    "method": "eth_subscribe",
    "params": ["newHeads"]
  }));
});

ws.on('message', (data) => {
  const response = JSON.parse(data);
  console.log('New block:', response);
});

注：

• 使用 /evm for standard blockchain operations on recent blocks (HTTP only). The /evm endpoint does not retain historical data — older blocks are periodically pruned
• 使用 /nanoreth for transaction tracing, debugging, WebSocket subscriptions, and any historical data queries

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	推荐
Standard Queries	eth_getBlockByNumber	✅ Recent blocks only	✅ Full archive	/evm for recent, /nanoreth for historical
	eth_getBalance	✅ Recent blocks only	✅ Full archive	/evm for recent, /nanoreth for historical
	eth_getTransactionByHash	✅ Recent blocks only	✅ Full archive	/evm for recent, /nanoreth for historical
Transaction Ops	eth_sendRawTransaction	✅ Optimized	✅ Available	/evm
	eth_call	✅ Fast (latest only)	✅ All blocks	/nanoreth for historical data
调试 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

Important Notes

• Data retention on /evm: 该 /evm endpoint does not provide archival access. Older block data is periodically pruned (approximately every 12 hours). Requests for blocks outside the retention window will return an 块高度无效 错误。请使用 /nanoreth for any historical data needs
• Trace methods like debug_traceTransaction 以及 trace_transaction only work on /nanoreth endpoint
• Historical queries for eth_call method require /nanoreth - /evm only supports latest 块
• Rate limits are lower on debug and trace methods due to their higher computational overhead
• Timeouts should be set appropriately for complex trace operations to prevent request failures

Key Implementation Differences

该 /evm 以及 /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 in eth_getLogs responses and WebSocket subscriptions.

Transaction Hash Lookups:

• System transaction hashes return "transaction not found" on /evm endpoint. Use eth_getSystemTxsByBlockHash 以及 eth_getSystemTxsByBlockNumber methods to access system transactions on /evm.

Cross-Layer Integration

HyperEVM smart contracts can read HyperCore data (such as oracle prices) through precompile addresses. See the HyperCore Oracle Prices guide for implementation details.

HyperCore Service

HyperCore is Hyperliquid's native exchange layer, and Quicknode provides managed infrastructure access to its APIs. HyperCore provides real-time and historical access to trading data, order book updates, and exchange events. Access HyperCore through specialized endpoints supporting Info API, JSON-RPC, gRPC streaming, and WebSocket protocols.

HyperCore 信息端点

https://your-endpoint.hype-mainnet.quiknode.pro/your-token/info

Best for: Querying comprehensive market data, user information, and exchange state through specialized info methods. Use this endpoint to retrieve order books, user positions, trading history, vault analytics, funding rates, portfolio data, and real-time market prices. Supports 52 info methods covering perpetual and spot markets, user accounts, vaults, and delegations.

Example request:

curl -X POST https://your-endpoint.hype-mainnet.quiknode.pro/your-token/info \
  -H "Content-Type: application/json" \
  -d '{
    "type": "allMids"
  }'

Available Info Methods: Access market metadata (meta, spotMeta), user data (clearinghouseState, userFills, portfolio), order information (openOrders, orderStatus, historicalOrders), market data (l2Book, recentTrades, candleSnapshot), vault analytics (vaultDetails, vaultSummaries), funding data (fundingHistory, userFunding), and more. See the Info Endpoints documentation for complete method details.

HyperCore Method Compatibility

Quicknode's /info endpoint supports 50 of 52 Hyperliquid info methods natively. For l2Book 以及 近期交易, Quicknode offers purpose-built gRPC alternatives: StreamL2Book delivers full order book snapshots up to 100 price levels deep every block, and StreamData (TRADES stream) provides real-time trade data with lower latency than the native info method.

See the Info Endpoints reference for the full method list.

HyperCore Exchange API Endpoint

Best for: Trading operations, builder fee management, and market queries. Use this endpoint to build and sign orders, manage builder fee approvals, validate orders before signing, and discover available markets.

计划要求

如果您正在使用免费试用套餐，我们会为您提供一个 URL，但该 URL 并非专属于您的 Quicknode 账户。详情请参阅hyperliquidapi.com，如需支持，请访问我们的Discord 频道。

Available Method Categories:

• Build (no signature) - Build order actions that return hash to sign: orders, market orders, close position, cancel, modify, approve/revoke builder fee
• Send (with signature) - Submit signed actions to Hyperliquid: send order, cancel, modify, approval, revocation
• Enhanced Endpoints - Check approval status, query open orders with pre-built cancel actions, check order status with plain-English explanation, validate orders (preflight), list markets and DEXes

Example request (build order):

curl -s -X POST https://docs-demo.hype-mainnet.quiknode.pro/hypercore/exchange \
  -H "Content-Type: application/json" \
  -d '{
  "action": {
    "type": "order",
    "orders": [
      {
        "asset": "BTC",
        "side": "buy",
        "price": "100000",
        "size": "0.001",
        "tif": "ioc"
      }
    ]
  }
}'

Example request (list markets):

curl -s https://docs-demo.hype-mainnet.quiknode.pro/hypercore/markets

Example request (open orders):

curl -s -X POST https://docs-demo.hype-mainnet.quiknode.pro/hypercore/openOrders \
  -H "Content-Type: application/json" \
  -d '{
  "user": "0x8ae62e9a4775350022c1577b2eff694e2b72be8d"
}'

HyperCore HTTP/JSON-RPC Endpoint

https://your-endpoint.hype-mainnet.quiknode.pro/your-token/hypercore

Best for: Retrieving historical exchange data and performing on-demand queries. Use this endpoint to backfill missed data during connection interruptions, fetch specific blocks by number, or retrieve batches of up to 200 blocks at once for analysis and archiving purposes.

Example request:

curl -X POST https://your-endpoint.hype-mainnet.quiknode.pro/your-token/hypercore \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "method": "hl_getLatestBlocks",
    "params": {
      "stream": "trades",
      "count": 10
    },
    "id": 1
  }'

HyperCore gRPC Streaming Endpoint

your-endpoint.hype-mainnet.quiknode.pro:10000

HyperCore gRPC streaming provides access to all thirteen data streams with native zstd compression, reducing bandwidth by approximately 70%. Seven streams (BLOCKS, StreamL2Book, StreamL4Book, StreamBboBook, StreamL2BookDiff, StreamL4BookUpdates, StreamTpslUpdates) are available exclusively through gRPC. For web-based applications where gRPC client support is limited, the WebSocket endpoint provides access to six of the thirteen streams.

Best for: High-performance real-time data streaming applications that require low latency. Ideal for market makers, algorithmic trading systems, and applications that need continuous order book monitoring, live trade feeds, and instant order status updates with minimal overhead.

Example connection (JavaScript):

const grpc = require('@grpc/grpc-js');
const protoLoader = require('@grpc/proto-loader');

const endpoint = 'your-endpoint.hype-mainnet.quiknode.pro:10000';
const token = 'your-token';

const credentials = grpc.credentials.combineChannelCredentials(
  grpc.credentials.createSsl(),
  grpc.credentials.createFromMetadataGenerator((params, callback) => {
    const metadata = new grpc.Metadata();
    metadata.add('authorization', `Bearer ${token}`);
    callback(null, metadata);
  })
);

const client = new proto.StreamService(endpoint, credentials);

HyperCore WebSocket Endpoint

计划要求

Access to the HyperCore WebSocket (/hypercore/ws) requires a Build plan or higher. 查看价格 进行升级。

wss://your-endpoint.hype-mainnet.quiknode.pro/your-token/hypercore/ws

Best for: Browser-based and JavaScript applications that need real-time exchange data without the complexity of gRPC. Suitable for building trading dashboards, price monitors, portfolio trackers, and event-driven applications using standard WebSocket libraries available in any programming environment.

Example subscription:

const ws = new WebSocket('wss://your-endpoint.hype-mainnet.quiknode.pro/your-token/hypercore/ws');

ws.send(JSON.stringify({
  "method": "hl_subscribe",
  "params": {
    "streamType": "trades",
    "filters": {
      "coin": ["BTC", "ETH"]
    }
  }
}));

可用数据流

HyperCore endpoints provide access to fourteen data streams:

Stream Type	描述	API Support
行业	Executed trades with price and size	gRPC + JSON-RPC/WSS
订单	订单生命周期事件（18种以上状态类型）	gRPC + JSON-RPC/WSS
BOOK_UPDATES	Order book changes	gRPC + JSON-RPC/WSS
TWAP	TWAP execution data	gRPC + JSON-RPC/WSS
活动	Balance changes, transfers, deposits, withdrawals	gRPC + JSON-RPC/WSS
WRITER_ACTIONS	HyperCore ↔ HyperEVM 桥接数据	gRPC + JSON-RPC/WSS
BLOCKS	Raw blockchain data with all transaction types	gRPC only
StreamL2Book	聚合价格水平深度（每个区块的完整快照）	gRPC only
StreamL4Book	单笔订单簿（快照 + 每个区块的差异）	gRPC only
StreamBboBook	委托单顶部的最佳买价/卖价，仅在BBO发生变化时输出	gRPC only
StreamL2BookDiff	基于单枚代币序列号的L2价格水平增量变化	gRPC only
StreamL4BookUpdates	按订单类型编写的添加/更新/删除差异	gRPC only
StreamTpslUpdates	基于未平仓订单快照的触发（TP/SL）订单添加/删除更新	gRPC only
MEMPOOL_TXS	待处理的mempool交易	gRPC only

For complete details on data streams, filtering, and examples, see the Hyperliquid Data Streams documentation.

HyperCore Endpoints at a Glance

• /hypercore（简体中文（大陆）） : Hyperliquid's JSON-RPC API for historical block queries and WebSocket subscriptions
• /hypercore/exchange : Hyperliquid's REST API for trading operations (build/send orders, manage approvals)
• /hypercore/markets, /hypercore/openOrders, /hypercore/orderStatus : REST query endpoints for market and order data
• /hypercore/ws : WebSocket endpoint for real-time data stream subscriptions
• /info : Hyperliquid's market data and user query API (POST with {"type": "methodName"})
• :10000 (gRPC) : HyperCore gRPC streaming for real-time exchange data (separate port, not a URL path)

Choosing an API

With multiple access paths available, use the following guide to select the right API for your use case:

Goal	Recommended API	为什么
Query market data, user positions, order books	/info endpoint	Simple POST requests, 50 of 52 methods natively supported (see method compatibility note)
Stream real-time trades, orders, book updates (browser/web apps)	/hypercore/ws WebSocket	Browser-compatible, JSON-based, 6 data streams
Stream real-time data (high-performance/trading systems)	HyperCore gRPC streaming (port 10000)	Sub-millisecond latency, zstd compression, 13 data streams including L2/L4 book and BBO
Backfill historical exchange data	/hypercore（简体中文（大陆）） JSON-RPC	Batch queries up to 200 blocks
Build and submit trades	/hypercore/exchange REST API	Order lifecycle management with signature support
Monitor HyperEVM contract events (push-based)	Quicknode Streams	Webhook delivery, filter by address/topic
Run analytical queries on historical Hyperliquid data	SQL 资源管理器	SQL interface to indexed tables
部署智能合约并与之交互	/evm 或 /nanoreth	Standard Ethereum JSON-RPC
Debug or trace transactions	/nanoreth	debug_* 以及 trace_* 方法

Support & Resources

For technical support, visit Quicknode Support. For Hyperliquid protocol details, see the official documentation.

信贷使用情况

Different methods consume different amounts of credits: View Hyperliquid API credit costs →

速率限制

速率限制因套餐等级而异：查看详细定价和限制 →