Quicknode

August 19, 2026 — 9 min read

Hyperliquid sentry peering is a direct connection between a self-operated Hyperliquid non-validating node and dedicated sentry nodes, so the node receives blocks and the full mempool over stable, allowlisted peers instead of variable public root peers. It is the piece of running a Hyperliquid node that most teams struggle with, and the piece that determines whether your node's data is consistent enough to trade on.

This guide covers what sentry nodes are, why peering matters for market makers and node operators, every option for peering a node in 2026, and how Quicknode Hyperliquid Peering works at $500/month.

What is a sentry node on Hyperliquid?

Hyperliquid's network has three tiers of participants:

Validators run HyperBFT consensus. They propose and vote on blocks. The active set is the top validators by stake, and validator IPs are not exposed to arbitrary peers.

Sentry nodes are non-validating nodes operated alongside validators. In the official node software, each validator can register up to two non-validator peers as sentry_ips. Sentries sit one hop from consensus, absorb public traffic, and shield the validator. They can serve as root peers, API servers, and EVM RPCs.

Non-validating nodes are permissionless. Anyone can run one by following the Hyperliquid node repository. A non-validating node replays every block, exposes local data streams, and can power a local API server for real-time fills, orders, and book state.

The catch: a non-validating node is only as good as its peers. Your node learns about new blocks and pending transactions through gossip, and gossip quality depends entirely on who you are connected to.

Why peering is the hard part of running a Hyperliquid node

Standing up the node itself is well documented. Per the official requirements, a non-validating node needs 16 CPU cores, 128 GB RAM, a 500 GB SSD, Ubuntu 24.04, ports 4001 and 4002 open to the public, and ideally Tokyo placement, since that is where the validator set concentrates. The operational grind starts after applied block shows up in your logs.

Out of the box, your node connects to public root peers. You can query the current list at any time:

curl -X POST --header "Content-Type: application/json" \
  --data '{ "type": "gossipRootIps" }' \
  https://api.hyperliquid.xyz/info

Public root peers are free, and they come with three problems:

1. They are shared and variable. Root peers rotate, saturate, and disconnect. Your block delivery inherits whatever load they happen to be under. The result is inconsistent latency, and in particular fat tail latency: the occasional block that arrives seconds late, which is exactly the block a trading system cannot afford to miss.

2. Most do not pass the mempool. Receiving pending transactions from a peer requires that peer to be configured to forward them. Arbitrary public peers usually are not. If your strategy needs pre-confirmation visibility, public gossip alone will not deliver it.

3. Recovery after disconnects is slow. When a public peer drops you, your node has to rediscover a healthy peer through gossip before block flow resumes.

The alternative the docs point to is the Foundation non-validating node, which offers a reliable peer with fewer hops to validators. Direct peer access to it, however, has required staking 10,000 HYPE and holding Tier 1 maker rebate status, defined as more than 0.5% of 14-day weighted maker volume, and it is offered on a best-efforts basis with no availability guarantees. For most teams, that is a non-starter.

That leaves dedicated sentry peering: a paid, allowlisted connection to professionally operated sentry nodes.

What dedicated sentry peering actually changes

Sentry peering does not make your node faster than the rest of the network, and any provider claiming it puts you ahead of other participants is overselling. What it changes is the consistency of your connection:

• Tight block delivery. A dedicated peer one hop from a validator delivers blocks on a predictable path. The improvement shows up most in tail latency: the worst-case delays that public gossip produces largely disappear when your peers are stable and unsaturated.

• Full mempool delivery. Dedicated sentries can be configured to forward pending transactions, giving your node the raw mempool that public peers typically withhold.

• Fast recovery. With multiple allowlisted peers across datacenters, a single disconnect does not interrupt block flow, and reconnection does not depend on gossip discovery.

• Someone to call. Peering to operated infrastructure means a team monitors the sentry side of your connection.

For market makers, HFT systems, and any mempool-driven strategy on Hyperliquid, this is the difference between a node you can trade on and a node you babysit.

Quicknode Hyperliquid Peering: 3 sentry peer IPs, full mempool, $500/month

Quicknode Hyperliquid Peering is a flat-priced sentry peering service for teams running their own non-validating node.

A few details worth calling out:

The peers are sentries, not validators. You connect to non-validating sentry nodes that are themselves connected to a validator. Your peers do not participate in consensus, and peering involves no staking or delegation. Quicknode’s own non-validating nodes, the ones behind its managed Hyperliquid endpoints, peer through the same sentry layer.

The mempool is unmetered. At roughly 1.1 TB/day of observed raw mempool volume, per-GB pricing gets expensive fast. Quicknode includes full mempool delivery in the flat $500 with no separate usage meter.

Provisioning is manual by design. Allowlisting is per IP. A Quicknode engineer reviews each request, allowlists the node, and returns all three peer IPs with configuration guidance. There is no staking requirement, no volume threshold, and no application review of whether your firm is large enough.

Every way to peer a Hyperliquid node, compared

How to set up Hyperliquid sentry peering in 4 steps

1. Subscribe. Create a Quicknode account, then open Add-ons in your Quicknode dashboard and select the Hyperliquid Peering add-on to subscribe at $500/month. The subscription is charged at checkout, with a 7-day evaluation window from activation.

2. Send your node details. Email support@quicknode.com with your account email and your node's public IP.

3. Receive your peers. An engineer allowlists your node and returns all three sentry peer IPs with configuration guidance.

4. Configure and verify. Add the peer IPs to ~/override_gossip_config.json and set split_client_blocks: true. Pending transactions then stream to ~/hl/data/mempool_txs/ on your server. This is the standard Hyperliquid node mechanism, not a custom interface, so nothing about your tooling changes.

During the 7-day window, measure what matters: block latency distribution including p95 and p99, recovery time after forced disconnects, and sustained mempool delivery during volatile periods. If stability does not meet your requirements, contact support within the window for a prorated refund.

Sizing your server for the full mempool

Before enabling mempool delivery, check three things on the node host: inbound bandwidth headroom for 1.1+ TB/day, disk capacity and a retention policy for ~/hl/data/mempool_txs/, and log rotation, since a Hyperliquid node already produces heavy daily log output on its own.

Peering or a managed endpoint: which do you need?

The honest question is whether you want a node, or the data from a node.

Running your own non-validating node means a serious server, Tokyo placement, heavy daily log management, and a 24/7 operations commitment. If your team has already made that commitment, peering solves the hardest remaining problem. If you have not, a managed Quicknode Hyperliquid endpoint delivers blocks, trades, and transactions over JSON-RPC, WebSocket, gRPC, and Streams with instant self-serve setup and no node to operate.

Frequently asked questions

What is Hyperliquid sentry peering?

Hyperliquid sentry peering is a direct, allowlisted connection between a Hyperliquid non-validating node you operate and dedicated sentry nodes, delivering blocks and the full mempool over stable peers instead of variable public root peers. Quicknode offers it at $500/month for 3 dedicated peer IPs across multiple Tokyo datacenters.

Do I need to run my own Hyperliquid node to use peering?

Yes. Peering only helps if you already operate a Hyperliquid non-validating node. If you want Hyperliquid data without running infrastructure, use a managed Hyperliquid endpoint instead.

What are the hardware requirements for a Hyperliquid non-validating node?

Per the official repository: 16 CPU cores, 128 GB RAM, a 500 GB SSD, and Ubuntu 24.04, with ports 4001 and 4002 open to the public. Tokyo placement is recommended for lowest latency to the validator set.

How do I get the full Hyperliquid mempool?

Your node must peer with a sentry configured to forward pending transactions, with split_client_blocks: true set in ~/override_gossip_config.json. Transactions then stream to ~/hl/data/mempool_txs/. Public root peers typically do not forward mempool data; Quicknode sentry peers are configured for it, with no separate usage meter.

How much does Hyperliquid peering cost?

Quicknode Hyperliquid Peering is $500/month flat, including 3 dedicated sentry peer IPs, full unmetered mempool delivery, and a 99.99% uptime SLA. An active Quicknode plan is required. Peering to the Foundation non-validating node is free but has required 10,000 HYPE staked and Tier 1 maker rebate status.

Will sentry peering make my node faster than other traders?

No. Peering gives you a reliable, redundant path to blocks and the full mempool. It does not put you ahead of other network participants, and actual latency depends on where your node runs and your network path to the peers.

Where are Quicknode's Hyperliquid sentry peers located?

Across multiple datacenters in the Tokyo region, where Hyperliquid's validator set concentrates. All three peer IPs are shared after activation.

What happens if my server IP changes?

Allowlisting is per IP, so email support with the new address, ideally ahead of a planned migration, and the allowlist gets updated.

Peer your node

If you operate a Hyperliquid non-validating node and need dedicated peers, full mempool, and an SLA someone actually monitors, Hyperliquid Peering is live now. Create an account, add the Hyperliquid Peering add-on, send your node’s public IP, and an engineer will have you peered with all three sentries. Not running a node? Start with a managed Hyperliquid endpoint instead.