> For the complete documentation index, see [llms.txt](https://docs.luganodes.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.luganodes.com/tools-and-services/hyperliquid/hyperliquid-node-peering.md). # Hyperliquid Node Peering A private, allowlist-only peer connection between your Hyperliquid non-validating node and dedicated Luganodes peering nodes in Tokyo. Our peering nodes are dedicated non-validating nodes that peer directly with the Hyperliquid Foundation’s non-validating node as their upstream, under the Foundation’s infra-provider peering program. ### What you get * Dedicated peer IPs in the Tokyo region * Reliable block delivery and the full mempool transaction stream (split\_client\_blocks supported end to end) * No usage metering and no egress charges, so the monthly price is flat * Our nodes respect the on-chain gossip priority auction ordering; any read prioritization among connected peers is determined by the protocol’s open auction, not by us. * 24/7 monitoring, with a direct channel to the engineers who operate the infrastructure (email and Telegram/Slack). ### Uptime 99.5% availability per peer per calendar month, measured by gossip reachability of the peer IPs (ports 4001/4002). This SLA applies to our peers only. Your own node’s uptime sits outside its scope. ### Requirements * You run your own non-validating node per the official node documentation (Ubuntu 24.04, 16+ cores, 128 GB RAM, 500 GB+ NVMe recommended) * A static public IP for your node, with ports 4001/4002 reachable * Bandwidth and disk headroom for the full mempool stream (roughly 1 TB/day of inbound data at current network activity; size your pruning accordingly) ### Onboarding Activation is manual and typically completes within one business day: * Email **** with your node’s public IP. * We add your node to our allowlist and return both peer IPs with configuration guidance. * Restart your node. Mempool transactions are then written to \~/hl/data/mempool\_txs/ and blocks arrive via the standard gossip mechanism, with no custom interface and no API in the path. If your node’s public IP changes, contact us and we will update the allowlist. ### Notes * Peering uses Hyperliquid’s native P2P mechanism. It delivers data to your node; order submission continues to work exactly as before (via your own node or the public API). * The two peer IPs are for redundancy: maintenance on one host never leaves your node without a live upstream. * Our peering nodes are operated separately from our validator infrastructure. * For teams that want Hyperliquid data without running a node, managed gRPC streams from the same infrastructure are in early access; contact us.