Luganodes RPC is live. Built for enterprise, open to every builderLIVE

Research

9 min read

Hyperliquid Peering Provider: A Due-Diligence Checklist

What to ask before choosing a sentry peering provider

Hyperliquid Peering Provider: A Due-Diligence Checklist

Published on

November 17, 2026

Every Foundation-approved Hyperliquid peering provider relays the same Hyperliquid chain data. A peering provider runs a node that passes blocks and mempool data (transactions not yet committed to a block) to a client's own node. Upstream sources differ between providers, from the Foundation-run sentry (the Foundation non-validating node in Hyperliquid's documentation) to a provider's own validator sentries.

So the choice comes down to the path from upstream source to client node, the contract and the operator. Little has been published on SLAs (service level agreements) or vendor due diligence for sentry peering, so the eleven questions below give trading desks, prime brokers, liquidity bridges and exchanges a starting point.

The path and the data

1. Is the provider Foundation-approved, and what is its upstream source?

Approved providers meet the Foundation's standards for operating history, 99.9% uptime, non-discriminatory pricing and auto-scaling, and are listed on Hyperliquid's infrastructure provider page. A strong answer names the upstream source, such as the Foundation-run sentry, and how the validator set feeds it. Peering with the sentry directly is covered in [internal link: Two Routes to the Hyperliquid Foundation Non-Validating Node].

2. Where does the peer sit, and what path does the data take?

Hyperliquid's validator set is concentrated in Tokyo, and the Foundation non-validating node runs in AWS availability zone apne1-az1 (an isolated data center group). Each hop, or machine in the path, adds delay and a point of failure. A strong answer names the city, ideally the zone, and each hop.

3. Is mempool delivered end to end?

The split_client_blocks setting streams pending transactions only if every peer between the validators and the client node enables it, so the provider should confirm it at every hop. Hyperliquid's latency guidance says the setting can cut read latency by 70 to 150 ms.

4. Does the peer honor gossip priority ordering?

Hyperliquid allocates read priority through an open on-chain auction, but each hop in the gossip relay (the peer-to-peer network between nodes) may or may not respect it. A bidding firm needs a yes here; [internal link: The Hyperliquid Gossip Priority Auction, Hop by Hop] covers the mechanics.

Access and support

5. Is the peer slot reserved, and how many node IPs can connect?

Public peers are shared and their availability varies, which suits testing and backup. A reserved slot (set through reserved_peer_ips on the peer) means the client's connection is always accepted. A standby node needs its own allowlisted (permitted) IP, so the count belongs in the contract.

6. How fast is onboarding, and how are IP changes handled?

Onboarding time sets how soon a new or replacement node receives data, and the provider should commit to a time from receipt of the node IP. IP changes double as a security control: the buyer should know who may request one and how the provider verifies it.

7. Who answers when something breaks, and how is the client told?

Hyperliquid recommends Tokyo for node placement, so support has to cover Asia-Pacific hours, when staff in London or New York may be offline. A strong answer is a direct channel to the engineers running the peers, with support hours in writing. The provider should also have a written incident policy and give notice of network upgrades.

The contract

8. What exactly does the SLA cover?

A Hyperliquid node peering SLA usually covers the provider's peer, and the client's own node stays the firm's responsibility. The SLA schedule should define four terms:

  • Scope and window: whose availability counts, over what period.
  • Measurement: how availability is checked, and whether a connected peer that falls behind counts as up.
  • Exclusions: planned maintenance and its notice period.
  • A missed target: what the contract says happens next.

9. Are the terms the same for every client?

The Foundation's program requires non-discriminatory pricing and forbids preferential treatment of specific clients, such as market makers. A strong answer confirms in writing that price, configuration and treatment are identical for all clients.

The operator and its controls

10. Is the peering infrastructure separate from other services?

Many providers also run validators, RPC endpoints (API access to nodes) or data products. Separation limits how far a fault in one service can spread, and an architecture note should show what is shared.

11. What security and corporate evidence can the provider share?

Compliance teams can vet institutional Hyperliquid infrastructure like any market data supplier. The core requests are a SOC 2 Type II report (an auditor's opinion on whether controls worked over time), ISO 27001 status, the contracting entity, its jurisdiction and sanctions screening.

Evidence to request from a Hyperliquid peering provider

QuestionsEvidence to request
1 to 4: path and dataArchitecture note naming upstream source, city, zone and each hop; written split_client_blocks and gossip priority confirmation
5 to 7: access and supportOnboarding runbook; IP-change procedure; support hours and escalation contacts; incident policy
8 and 9: contractSLA schedule; written equal-terms statement
10 and 11: operator and controlsSeparation note; SOC 2 Type II report; ISO 27001 status; contracting entity and jurisdiction; sanctions policy

How Luganodes answers the core questions

  • Path and data (1 to 4). Luganodes is a Foundation-approved provider. Every subscription includes full blocks and mempool over a fixed, short path: Foundation validator set, Foundation-run sentry, Luganodes peer node in Tokyo, client node. Luganodes peers respect on-chain gossip priority ordering; read prioritization among connected peers is determined by the protocol's open auction.
  • Access and support (5 to 7). One dedicated peer IP is reserved for the client's node. Two node IPs are allowlisted by default, and more can be added. Nodes are peered within 24 hours of receiving the node IP. IP changes go through the client's engineer channel, and clients have a direct channel to Luganodes node engineers.
  • Contract (8 and 9). The 99.9% contractual uptime SLA covers the availability of the dedicated Luganodes peer; the client's own node sits outside it. Luganodes meets the Foundation's non-discriminatory pricing standard, and every client receives the same terms.
  • Operator and controls (10 and 11). Peering nodes run separately from Luganodes' validator infrastructure. Luganodes holds SOC 2 Type II certification and operates in alignment with ISO 27001:2022.

Trading and connectivity teams can send this checklist to business@luganodes.com for Luganodes' answers in writing. Service details are on the Hyperliquid peering product page.

Frequently Asked Questions

What should a Hyperliquid peering SLA cover?

A Hyperliquid peering SLA should define whose availability it covers, the uptime target, the measurement window and method, exclusions such as planned maintenance, and what happens when the target is missed. Peering SLAs normally cover the provider's peer, so the client's own node stays the firm's responsibility. Luganodes' 99.9% contractual uptime SLA, for example, covers the availability of the dedicated Luganodes peer; the client's node sits outside it.

Do all approved Hyperliquid peering providers deliver the same data?

Yes, at the source: every approved provider relays the same Hyperliquid chain data (blocks and mempool). Upstream sources differ between providers, from the Foundation-run sentry to a provider's own validator sentries. What a given node receives still depends on delivery: whether split_client_blocks is enabled at every hop, whether the peer slot is reserved, and how the path is monitored and supported.

Does peering change how a firm sends Hyperliquid orders?

No. Peering is a read path that delivers blocks and mempool to the firm's node. With Luganodes peering, order submission works exactly as before.

What documents should a firm request from a peering provider?

A firm should request an architecture note showing the upstream source and every hop, the SLA schedule, an onboarding runbook with the IP-change procedure, and the incident communication policy. Compliance teams should add a SOC 2 Type II report, the provider's ISO 27001 status, the contracting entity and jurisdiction, and the sanctions screening policy. Asking every provider on a shortlist for the same set makes the answers comparable.

Is Luganodes SOC 2 Type II certified?

Yes. Luganodes holds SOC 2 Type II certification and operates in alignment with ISO 27001:2022. On Hyperliquid, Luganodes is a Foundation-approved peering provider, has operated on the network since testnet and runs a validator today.

About Luganodes

Luganodes is a world-class, non-custodial blockchain infrastructure provider that has rapidly gained recognition in the industry for offering institutional-grade services. It was born out of the Lugano Plan B Program, an initiative driven by Tether and the City of Lugano. Luganodes maintains an exceptional 99.9% uptime with round-the-clock monitoring by SRE experts. With support for 40+ PoS networks and serving 60+ institutional clients, it ranks among the top validators on Polygon, Polkadot, Sui, and Tron. Luganodes prioritizes security and compliance, holding the distinction of being one of the first staking providers to adhere to all SOC 2 Type II, GDPR, and ISO 27001 standards as well as offering Chainproof insurance to institutional clients.

The information herein is for general informational purposes only and does not constitute legal, business, tax, professional, financial, or investment advice. No warranties are made regarding its accuracy, correctness, completeness, or reliability. Luganodes and its affiliates disclaim all liability for any losses or damages arising from reliance on this information. Luganodes is not obligated to update or amend any content. Use at your own risk. For specific guidance, please consult a qualified professional.