Hyperliquid sentry peering. 3 peer IPs. $500/month.

A direct connection between a Hyperliquid node you operate and Quicknode’s sentry nodes, so your node receives blocks and the full mempool over dedicated peers instead of variable public root peers. Peering is $500/month for 3 dedicated peer IPs across multiple datacenters in the Tokyo region.

Yes. Peering is only useful if you already operate your own Hyperliquid non-validating node. Quicknode does not run the node for you. If you want Hyperliquid blocks, trades, or transactions delivered to your application without running node infrastructure, use a Quicknode Hyperliquid endpoint over gRPC or WebSocket instead.

Peering connects a node you run to our sentry peers for redundant blocks and the full mempool. A managed Quicknode Hyperliquid endpoint is an API we run for you, delivered over JSON-RPC, WebSocket, gRPC, and Streams. Peering suits teams that have already committed to their own node; a managed endpoint suits everyone else.

Public root peers are free but shared and variable, and many are not configured to pass mempool data. Peering to the Hyperliquid Foundation’s non-validating node requires 10,000 HYPE staked and Tier 1 maker rebate status, meaning over 0.5% of 14-day weighted maker volume. Quicknode peering has no staking or volume requirement.

No. Peering gives you a reliable, redundant path to blocks and the full mempool without per-MB metering. It does not put you ahead of other peers, and the three IPs are for redundancy, not for an edge. Actual latency depends on where your node runs and your network path to our peers.

Sentries. You connect to non-validating sentry nodes that are themselves connected to a validator. Every validator has two sentry peers. Your peers do not participate in consensus, and peering does not involve staking or delegation. Our own non-validating nodes peer through the same sentry layer.

Yes. Mempool streaming is included with no separate usage meter. Getting mempool from a peer requires that peer to be configured to pass it, which is why arbitrary public peers often do not deliver it. Quicknode sentries are configured for mempool delivery.

Observed raw mempool volume is approximately 1.1 TB/day and varies with network activity, running higher during volatile periods. Size your server’s bandwidth, disk capacity, and retention policy accordingly before you provision.

The peers are across multiple datacenters in the Tokyo region. We share the IPs after you sign up and add you to our allowlist.

Three. All three are returned at activation.

You add our peer IPs to ~/override_gossip_config.json and set split_client_blocks: true. Mempool transactions are then written to ~/hl/data/mempool_txs/ on your server. This is the standard Hyperliquid node mechanism, not a custom Quicknode interface.

Yes. Peering is an add-on and requires an active Quicknode plan alongside the monthly peering fee.

Activation is manual. Email support@quicknode.com with your Quicknode account email and the node’s public IP address. An engineer reviews the request, allowlists your node, and returns all three peer IPs with configuration guidance.

Email support and we will update the allowlist. Allowlisting is per IP, so any change to your node’s public IP needs to be sent to us. Send the new IP ahead of a planned migration.

Yes. The subscription is charged at checkout, but you have 7 days from activation to test latency, disconnect recovery, uptime, and sustained mempool delivery. Contact us within that window for a prorated refund if stability does not meet your requirements. To check fit before subscribing, email support@quicknode.com.

Availability of your sentry peer connections, monitored and alerted by the team that operates them. It does not cover the uptime of your own node.

The engineers who operate the sentry layer. Support is by email with APAC coverage, and we can open a shared channel with a named engineer for setup and ongoing operations.