Research
9 min read
Hyperliquid Foundation Non-Validating Node: Two Routes
Direct access and approved peering, read side by side.
Published on
November 6, 2026
Introduction
Trading firms have two documented ways to reach the Hyperliquid Foundation non-validating node, and eligibility and risk tolerance settle the choice long before speed comes into it. The node sits in Tokyo, close to Hyperliquid's validators, and is referred to below as the Foundation-run sentry. A firm can peer with it directly (connect its own node to it as an upstream source) if the firm meets the Foundation's criteria. Otherwise, the firm can peer through a provider the Foundation has approved and whose own peer is fed by the Foundation-run sentry.
Consider a market-making desk that already runs its own node in Tokyo. If the firm has 10,000 HYPE staked and its maker volume places it in Maker Rebate Tier 1, it can apply to connect to the Foundation-run sentry directly. If it misses either test, its route to the same source runs through a provider on the Foundation's list that peers with the Foundation-run sentry.
The Hyperliquid Foundation non-validating node runs on best-efforts terms
A non-validating node follows the chain and relays its blocks and transactions to other nodes without taking part in consensus. The Hyper Foundation operates a non-validating node in AWS availability zone apne1-az1 in Tokyo, offered so that peered nodes sit fewer hops from the validating nodes. Connecting to it is often called sentry peering, after the sentry nodes that relay data on behalf of validators.
Under the Foundation's documented terms, the Foundation-run sentry carries no guarantees on availability, latency, performance or completeness, and it should not be the sole or authoritative source for time-sensitive trading. Access can be modified, rate-limited or discontinued without notice.
A risk committee should read best-efforts terms as an allocation of risk. The Foundation supplies a well-placed source without a service commitment, so the cost of an interruption or a data gap stays with the connecting firm.
What changed in 2026
The gossip priority auction went live in April 2026, opening to on-chain bidding the order in which participating nodes send blocks and pending transactions to their peers. Changes to public WebSocket feeds were announced in June 2026, and automated traders were told to run their own non-validating nodes.
A firm that runs its own node needs a reliable upstream peer. In July 2026, Blockworks Research found 23 of 27 operator sentry endpoints full, a snapshot of capacity at that moment. In August 2026, the Foundation opened its node to approved infrastructure providers, which created the second route.
Route one: direct access and the Foundation node requirements
Direct access means the firm's own node peers with the Foundation-run sentry, with no provider in between. The Foundation publishes the criteria on its Foundation non-validating node page, and a firm must meet all of them:
- Stake. At least 10,000 HYPE staked.
- Maker volume. Maker Rebate Tier 1 or above, the fee-rebate tier for makers with more than 0.5% of 14-day weighted maker volume.
- A reliable connecting peer. The connecting node must be a reliable public peer with 98% time-weighted uptime, and the Foundation advises monitoring and alerting on it.
- Compliance. Adherence to applicable laws, sanctions and jurisdiction restrictions, including certain activities involving the U.S. or Ontario.
A firm may combine linked trading and staking accounts to meet the criteria. The Foundation may change the criteria at any time, and eligibility ends when a firm stops meeting them.
Because the uptime standard applies to the firm's own node, the direct route asks for an operating commitment as well as capital. Advice that names the Foundation-run sentry as a default primary peer often skips the eligibility gate, which decides whether the advice applies at all.
Route two: Foundation-approved peering providers
The second route runs through an infrastructure provider whose own peer connects to the Foundation-run sentry, which the Foundation opens to listed providers as an upstream peer. Upstream sources vary across listed providers, so the connection is worth confirming with each one.
The Foundation's infra-providers page lists the providers that have committed to offer peering to the public on its terms. A provider's clients skip the direct-access criteria, because the provider meets a separate Foundation standard. The program's criteria cover four areas:
- Standing. A reputable provider with strong SLAs (service level agreements, the contracted uptime and support terms) and a diverse builder base.
- Track record. At least one year of operation, at least 100 clients across at least five networks, and no for-cause termination in the prior three months.
- Service. 99.9% uptime and auto-scaling with the number of connected peers.
- Fair access. Open access with non-discriminatory pricing, and no preferential treatment of specific clients, such as market makers.
What approval establishes, and what stays with the buyer
Foundation approval sets a floor: every listed provider has committed to the same baseline on uptime, access, pricing and capacity. Clients can report problems with a listed provider's service to the Foundation through a contact on the infra-providers page. Above the floor, providers differ in upstream source, the delivery path to the client's node, SLA scope, support model and security posture. Each belongs in due diligence, and [internal link: Choosing a Hyperliquid Peering Provider: A Due-Diligence Checklist] works through them.
The routes side by side
Mempool data (pending transactions not yet committed to a block) reaches a node only when every peer between that node and the validating network streams it. So the mempool row differs by route.
| Public peers | Direct Foundation access | Foundation-approved provider | |
|---|---|---|---|
| Who can use it | Any node operator, capacity permitting | Firms meeting the criteria | Any team that subscribes |
| Eligibility | A correctly configured node | 10,000 HYPE staked, Maker Rebate Tier 1, a reliable public peer at 98% uptime, compliance | Provider's terms; open access is required |
| Service commitment | None; shared capacity that varies | Best-efforts; no guarantees; access can change without notice | 99.9% uptime required; contract set by each provider |
| Mempool | Depends on every peer in the path | Available from the Foundation-run sentry | Depends on the provider's configuration |
| Upstream path | Varies by peer and over time | Direct to the Foundation-run sentry | Via the provider's peer; upstream source and design vary by provider |
| Best suited to | Testing, development and backup | Eligible firms that accept best-efforts terms | Teams outside the criteria, or adding a contracted path |
Why eligible desks still keep a contracted second path
Qualifying for direct access leaves the best-efforts terms unchanged. A desk whose only upstream is the Foundation-run sentry relies on a source the Foundation itself says should not be the sole one for time-sensitive trading.
Eligibility can also lapse. Maker Rebate Tier 1 is measured on 14-day weighted maker volume, so a quieter fortnight can take a firm below the bar. The Foundation can also revise its criteria at any time. A contracted peer keeps the node supplied through either event, with an uptime commitment and a named counterparty behind it.
Redundancy is the third reason. Provider documentation describes a Hyperliquid node streaming from one upstream peer at a time, so a second configured peer gives it somewhere to reconnect when that link drops. A peer from a contracted provider also covers failures at the provider or host level, while any path that depends on the Foundation-run sentry shares that upstream.
Luganodes on the approved route
Luganodes is a Hyperliquid Foundation-approved peering provider under the Foundation's non-validating node program. The Luganodes peer node receives blocks and mempool from the Foundation-run sentry, which is fed directly by the Foundation validator set. Each client's node therefore sits on a fixed, short path: Foundation validator set, Foundation-run sentry, Luganodes peer node, client node.
Access is by subscription, with no HYPE staking or trading volume requirement. Each subscription includes one dedicated peer IP in Tokyo, reserved for the client's node, and carries full blocks and mempool transactions. A 99.9% contractual uptime SLA covers the availability of the dedicated Luganodes peer (the client's own node sits outside its scope).
Luganodes has operated on Hyperliquid since testnet and runs a validator on the network today. The company holds SOC 2 Type II and is ISO 27001:2022 certified.
Desks weighing the two routes, including eligible desks that want a contracted path next to direct access, can take their questions to business@luganodes.com. Once Luganodes receives a node IP, the node is peered within 24 hours. The Luganodes Hyperliquid peering page sets out the full service.
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.