> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hyperdash.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Direct Sentry Peering

> A private, whitelisted peer connection between your Hyperliquid node and Hyperdash sentry infrastructure.

Teams running their own Hyperliquid nodes depend on peers for market data. Public gossip peers are capacity-constrained, disconnect without notice, and degrade under load, particularly around network upgrades.

<Note>
  **Direct Sentry Peering is a private, whitelisted connection between your node and Hyperdash sentry infrastructure, which peers directly with a Hyperliquid Foundation node.** No middle layers between the Foundation peer and your node.
</Note>

## Who it is for

Teams that already run, or are ready to run, their own non-validating Hyperliquid node and want a stable path to the network:

* Market makers and latency-sensitive trading firms
* Quant and research funds
* Data and analytics providers
* Infrastructure teams building on Hyperliquid

## Peering or a hosted feed

Sentry peering removes the distribution layer entirely. Any hosted feed has to receive, process and rebroadcast data before it reaches you. With direct peering, your node receives blocks over Hyperliquid's native gossip protocol and you decode locally.

Peering suits teams already running their own node. If you would rather not operate one, talk to us about API access instead.

## What you get

* **Blocks and state updates** over Hyperliquid's native gossip protocol
* **Mempool transactions.** Our infrastructure runs `split_client_blocks` end to end, so `mempool_txs` populate on your node
* **Three whitelisted IPs** included, reserved for your nodes rather than shared capacity
* **Further IPs** on request, so you can move from staging to production without re-onboarding

We are never in your execution path. Order submission goes directly to Hyperliquid's API.

## Regions

| Region | Location | Status |
| - | - | - |
| Japan | Tokyo | Active |

Place your node in Tokyo, in the same region as the sentry. Fewer hops mean lower tail latency to fills, blocks and state updates. Actual improvement depends on your own infrastructure, region and processing pipeline, and gossip-layer latency is set by the network.

## Before you start

You will need a non-validating Hyperliquid node that you operate, on a machine with a static public IP. Hardware, operating system and port requirements are set by Hyperliquid, not by us: see the [Hyperliquid node repository](https://github.com/hyperliquid-dex/node) for current specifications.

Size disk and bandwidth for mempool capture before you enable it. `mempool_txs` is written continuously and is significantly larger than block data alone.

## Setup

<Steps>
  <Step title="Whitelist">
    Send us the static IP of your node. We whitelist it to our sentry node and return the sentry IP for your region.
  </Step>

  <Step title="Configure">
    Set our sentry IP as the root entry in your override gossip config, at `~/override_gossip_config.json`:

    ```json theme={null}
    {
      "root_node_ips": [{ "Ip": "<sentry-ip-we-provide>" }],
      "try_new_peers": false,
      "chain": "Mainnet"
    }
    ```

    Setting `try_new_peers` to `false` keeps your node on the reserved peer instead of drifting back onto public ones.
  </Step>

  <Step title="Activate">
    Restart your node and confirm blocks are applying. You are live on a fast, stable, always-on connection.
  </Step>
</Steps>

## Uptime and support

* Production infrastructure maintained to Hyperliquid Foundation standards
* 24/7 monitoring and alerting
* Direct channel to our infrastructure team

## Trial period

* A **complimentary trial period** to benchmark against your existing setup from your own machines

## Pricing

**\$500 per month, or \$5,000 per year**, including three whitelisted IPs.

* Further discounts for staking HYPE to our validator

## FAQ

<AccordionGroup>
  <Accordion title="How does this differ from consuming a websocket feed or API?">
    Sentry peering removes the distribution layer entirely. Any hosted feed must receive, process and rebroadcast data before it reaches you. With direct peering, your node receives blocks over Hyperliquid's native gossip protocol and you decode locally.
  </Accordion>

  <Accordion title="What latency improvement should we expect?">
    Results depend on each firm's infrastructure, region and processing pipeline, and gossip-layer latency is set by the network. The trial period exists so you can measure it from your own machines rather than take a number on trust.
  </Accordion>

  <Accordion title="Where does the sentry get its data?">
    The sentry peers directly with a Hyperliquid Foundation node. It originally peered with our validator infrastructure, which was the lowest-latency path at the time. Since Hyperliquid changed its gossip architecture, direct peering with the Foundation node is the fastest path. That Foundation peer is dedicated to our sentry.
  </Accordion>

  <Accordion title="How does the sentry compare to public peers?">
    Public gossip peers are capacity-constrained and disconnect without notice, particularly around network upgrades. Your peer here is reserved for your node.
  </Accordion>

  <Accordion title="Is mempool data included?">
    Yes. Our infrastructure runs `split_client_blocks` end to end, so `mempool_txs` populate on your node.
  </Accordion>

  <Accordion title="Are you in our execution path, and is our activity private?">
    No. Order submission goes directly to Hyperliquid's API. We are never in the execution path.
  </Accordion>

  <Accordion title="What is the uptime commitment?">
    The sentry runs on production infrastructure maintained to Hyperliquid Foundation standards, with 24/7 monitoring and alerting.
  </Accordion>

  <Accordion title="Can we change or add whitelisted IPs?">
    Yes. Three are included, and they can be swapped as you move from staging to production. Further IPs can be added on request.
  </Accordion>
</AccordionGroup>

## Access

To get access, email [sales@hyperdash.com](mailto:sales@hyperdash.com) or reach us on [Telegram](https://t.me/hyperhans).

## About Hyperdash

[Hyperdash](https://hyperdash.com) is a global trading platform and data analytics company. Direct Sentry Peering runs on our production infrastructure.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.