Hyperliquid Sentry Peering | ZAN

Hyperliquid Sentry Peering | ZAN

ZAN operates a Hyperliquid non-validating node in Tokyo and peers directly with the Hyperliquid Foundation node. With a Sentry Peer subscription, you connect directly to our node for a stable, low-latency upstream — combining Asia-Pacific local presence with enterprise-grade operations.

Pricing: 199 USD per month (flat, no volume tiers, no negotiated rates, not tied to staking or trading volume). This price covers stable peering for the committed block data baseline; To activate, email [email protected] with your organization name, the node's public IPv4, and its region.

Why choose ZAN sentry peer

• Stable peering. Hyperliquid public seed nodes rate-limit aggressively and rotate; ZAN's sentry peer is dedicated to your egress IP via an allowlist, with no contention for slots.
• Asia-Pacific local, Tokyo low latency. The node is in Tokyo — zero extra hops for APAC builders — with engineer support during APAC hours, so issues never sit in a self-service ticket queue.
• You run your node, we run the upstream. You operate your own non-validating node; ZAN supplies a reliable upstream peer with monitoring, alerting, and primary/standby failover.
• Multi-product synergy, one integration, multiple capabilities. The same connection can be combined with ZAN's Solana trading acceleration, AI Scan smart-contract auditing, multi-chain RPC, and more.

Onboarding steps

1. Request access

Send us the public egress IP of the machine that will run your node. We addlist it on the sentry fleet and return your root / reserved peer addresses within 2–5 business days.

2. Provision a machine

Meet the Hyperliquid node machine specs, and run in or near Tokyo to minimize round-trip latency

3. Point your node at ZAN sentry peers

Write the peer addresses ZAN provides into override_gossip_config.json in your node's home directory.

Committed block baseline (default):

{
  "root_node_ips": [{ "Ip": "<zan-peer-1>" }, { "Ip": "<zan-peer-2>" }],
  "try_new_peers": false,
  "chain": "Mainnet"
}

• try_new_peers: false keeps your node pinned to the ZAN sentries instead of drifting onto public peers.

4. Run your node

Start hl-visor, using the official hyperliquid-dex/node repository binary, and verify its signature.

5. Verify sync

• Check the newest block file to confirm the height is tracking the network applied block X signal).
• ZAN provides a connection-health monitoring dashboard and latency evidence (p50/p99 applied-height gap) so you can self-check connection quality.

SLA & operations

• Availability: ZAN commits to 99.9% reserved peer-connection availability with 24/7 monitoring and alerting. This SLA covers ZAN-side peer availability; the availability of your own node is your operational responsibility.
• Failover: Primary/standby nodes with persistent state volumes; ZAN pre-notifies and configures a transition IP when its node IP changes, to avoid connection interruption.
• Handling of sensitive data: The public IP you provide and the peer addresses ZAN returns are treated as sensitive — never committed to a repo and never printed in public logs.
• Upgrades & incidents: Node binaries follow official releases, with the visor signature-verification process fixed; maintenance windows and urgent incidents are communicated to you in advance.

ZAN — Powered by AntChain OpenLab | ISO/IEC 27001 · 27701 · 20000-1 · 22301 · 9001
This onboarding guide is for builder customers. ZAN provides a stable, low-latency dedicated upstream on top of the read-only baseline; raw mempool uncommitted-transaction flow, if needed, is delivered via a separate channel as a value-added capability, priced separately.