Vai al contenuto

Subscribe to Hyperliquid (Edge)

By connecting to DoubleZero I agree to the DoubleZero Terms of Use. Please note that the data is for your internal purposes only and may not be retransmitted (see Section 2(e)).

The Hyperliquid feeds deliver market data over DoubleZero Edge as UDP multicast. Four core feeds cover Hyperliquid native perps (hl) and trade.xyz perps (xyz):

Feed Description
hyper-hl-tob Best bid/offer and trade prints for Hyperliquid perps
hyper-hl-mbo Full order-by-order book for Hyperliquid perps (adds, cancels, executions)
hyper-xyz-tob Best bid/offer and trade prints for trade.xyz perps
hyper-xyz-mbo Full order-by-order book for trade.xyz perps (adds, cancels, executions)

Service overview: Hyperliquid.

Which path should I take?

Mode What you get When to use
Edge Connect doublezero-edge-connect — decode + normalized JSON WebSocket Fastest to a usable quote stream
Native multicast Subscribe on doublezero1, decode binary UDP yourself (or with reference parsers) Full control of the wire

Shared steps first: firewall, metro, apply, and pay (Steps 1–3). After approval, Step 4 splits — Edge Connect or native. Do not mix them on the same host.

Want an AI to do the install with you? Connect the DoubleZero MCP and ask it to walk you through Hyperliquid Edge.

Step 1: DoubleZero Setup

Complete Setup

Follow the setup instructions to install and configure the DoubleZero client on the host.

If you have previously set up DoubleZero on the host for native use, ensure the client is current:

sudo apt update && sudo apt install doublezero

Configure the Firewall

Allow GRE, BGP, PIM, and Hyperliquid feed traffic on doublezero1. Hyperliquid UDP ports sit in 20000–20999 (Top-of-Book and Market-by-Order market, reference, and snapshot). Also allow UDP 5765 for DoubleZero heartbeats on the tunnel. Open the feed band so new feeds do not need another firewall change. See Feed addresses.

iptables:

sudo iptables -A OUTPUT -p gre -j ACCEPT
sudo iptables -A INPUT -i doublezero1 -s 169.254.0.0/16 -d 169.254.0.0/16 -p tcp --dport 179 -j ACCEPT
sudo iptables -A OUTPUT -o doublezero1 -s 169.254.0.0/16 -d 169.254.0.0/16 -p tcp --dport 179 -j ACCEPT
sudo iptables -A OUTPUT -o doublezero1 -p pim -j ACCEPT
# Hyperliquid market / reference / snapshot (all feeds)
sudo iptables -A INPUT -i doublezero1 -p udp --dport 20000:20999 -j ACCEPT
# DoubleZero heartbeats
sudo iptables -A INPUT -i doublezero1 -p udp --dport 5765 -j ACCEPT

UFW:

sudo ufw allow proto gre from any to any
sudo ufw allow in on doublezero1 from 169.254.0.0/16 to 169.254.0.0/16 port 179 proto tcp
sudo ufw allow out on doublezero1 from 169.254.0.0/16 to 169.254.0.0/16 port 179 proto tcp
sudo ufw allow out on doublezero1 proto pim from any to any
# Hyperliquid market / reference / snapshot (all feeds)
sudo ufw allow in on doublezero1 to any port 20000:20999 proto udp
# DoubleZero heartbeats
sudo ufw allow in on doublezero1 to any port 5765 proto udp

You may tighten these rules to only the ports for the feeds you subscribe to (see Feed addresses).

Step 2: Choose a metro

Identify the lowest-latency location from the machine that will receive the feed:

doublezero latency

Note the metro / city from the lowest-latency result. You will select that city on the application form. See the topology map for how metros are grouped.

Pricing

Feeds are priced by delivery region. The price follows where the data is delivered, not where the buyer is. A Tokyo package delivers to Tokyo receivers; delivery elsewhere needs the Global package. Two receiving hosts (IPs) are included per feed, per metro.

Feed Tokyo /mo Global /mo
Hyperliquid perps Top-of-Book (L1) $900 $1,500
Hyperliquid perps Market-by-Order (L4) $3,000 $5,000
trade.xyz perps Top-of-Book (L1) $900 $1,500
trade.xyz perps Market-by-Order (L4) $3,000 $5,000
All feeds (bundle ~30% discount) $5,500 $9,000

Step 3: Submit Request

  1. Go to https://doublezero.xyz/edge/subscribe.
  2. Select Hyperliquid and the feeds you need.
  3. Select the city (metro) you need. Use the table above and doublezero latency to choose.
  4. Finish the application form.

You will assign a DoubleZero ID (existing key, or generate a new one) to each feed request on the accounts page. The matching private key must be present on the machine that will receive the feed — do not assign a pubkey whose private key you cannot move to that host.

You pick a metro and a pubkey. You do not bind a public IP at application time. During the subscription you can move access between IPs within the chosen metros.

You will be contacted with more instructions in a timely manner (expect 1-3 business days).

Step 4: Connect after approval

After you submit the application, you will receive an invoice; once it is paid, connect on each approved machine. Access is enabled on your chosen start date. Pick one path below.

4a. Edge Connect

If a host doublezerod is already running (from setup), stop it first — it fights the container’s daemon for the same tunnel:

sudo systemctl stop doublezerod

Install doublezero-edge-connect after approval and payment. The bridge joins DoubleZero inside a --network host container and serves normalized JSON on ws://<host>:8081.

curl -fsSL https://get.doublezero.xyz/connect | bash

All doublezero commands go through the container, not the host CLI:

docker exec doublezero-edge-connect doublezero status

Tip

You can create an alias for easy commands to the container. This example enables dz status to work the same as doublezero status inside the container:

echo "alias dz='sudo docker exec -it doublezero-edge-connect doublezero'" >> ~/.bashrc && source ~/.bashrc

Expect BGP Session Up and your edge-hyper-… group(s) subscribed.

Then open the WebSocket (ws://127.0.0.1:8081). Contract: PROTOCOL.md. Full walkthrough: MCP runbook hyperliquid-edge.

4b. Native multicast

On the host that holds the assigned private key (with host doublezerod running), subscribe to the feeds you purchased:

doublezero connect multicast --subscribe-feed <feed-code>

Multiple feeds, space-separated:

doublezero connect multicast --subscribe-feed hyper-hl-tob hyper-hl-mbo hyper-xyz-tob hyper-xyz-mbo

Check the tunnel:

doublezero status

Expect BGP Session Up on the correct DoubleZero network. Then decode the wire yourself — see Decode the feed.

Billing

Seats are charged monthly. Watch the seat expiration date.

You need to pay the invoice before the seat expires. Not paying leads to removal of the seat.

Feed addresses

IP picks the multicast group. Port picks the stream on that group. Check IP live values with:

doublezero multicast group list
Feed Description Multicast group Market Reference Snapshot Spec
hyper-hl-tob Best bid/offer and trade prints for Hyperliquid perps 233.84.178.27 20000 20001 — top-of-book
hyper-hl-mbo Full order-by-order book for Hyperliquid perps 233.84.178.28 20010 20011 20012 market-by-order
hyper-xyz-tob Best bid/offer and trade prints for trade.xyz perps 233.84.178.29 20100 20101 — top-of-book
hyper-xyz-mbo Full order-by-order book for trade.xyz perps 233.84.178.30 20110 20111 20112 market-by-order

Each feed has its own multicast group address. Ports: reference = market + 1; snapshot (MBO only) = market + 2. We suggest binding market and reference together; for MBO, also bind snapshot.

You may also see small UDP packets on port 5765 on doublezero1 — DoubleZero heartbeats, not market data.

Frames are little-endian fixed-size binary. Hyperliquid native perps use source_id=1; trade.xyz perps use source_id=7.

Decode the feed

Edge Connect

If you’re using doublezero-edge-connect, the feed is already decoded as JSON over WebSocket — skip manual decoding.

Use a reference parser

edge-multicast-ref ships multicast subscribers that decode the wire format and republish it as JSON on a Unix socket:

See the main README for the full pipeline.

Write your own decoder

Decode against edge-feed-spec. Start with the frame header, then the message layouts for the feed you are receiving.

GRE Tunnel Header — XDP

Market-data traffic delivered over the network is GRE-encapsulated at the last mile. On doublezero1, the client presents plain UDP multicast. If you terminate GRE yourself (e.g. an XDP pipeline), strip the GRE header before feeding data into your decoder. See gre-decap.

Troubleshooting

If you run into an issue not covered here, please reach out over your existing channel before working around it. If you do not have a channel, see Support.

Ensure your client is up to date

sudo apt update && sudo apt install doublezero

Tunnel not coming up

  1. Edge Connect: run status in the container — docker exec doublezero-edge-connect doublezero status. Host doublezero status often fails while the feed is fine (container owns the daemon). Confirm host doublezerod is stopped.
  2. Native: verify the host daemon is running: sudo systemctl status doublezerod
  3. Verify firewall rules are in place (GRE, BGP, PIM, Hyperliquid UDP ports and 5765 on doublezero1)
  4. Confirm the invoice for this seat is paid and the start date has passed
  5. Run connect on the path you chose (4a or 4b) with the key that matches the accounts page
  6. Expect BGP Session Up from the same place you ran connect (container or host)

No packets after subscribe

  1. Confirm you are subscribed: doublezero user list
  2. Confirm the feed appears under your groups: doublezero multicast group list
  3. Capture on the tunnel, e.g. Hyperliquid TOB: sudo tcpdump -ni doublezero1 host 233.84.178.27
  4. Prefer binding market and reference together (and snapshot for MBO) for the feed you want

Purchased feed missing (Edge Connect)

If a purchased feed is missing from doublezero status, subscribe inside the container:

docker exec doublezero-edge-connect \
  doublezero connect multicast --subscribe-feed <feed-code>

Multiple feeds, space-separated:

docker exec doublezero-edge-connect \
  doublezero connect multicast --subscribe-feed \
    hyper-hl-tob hyper-hl-mbo hyper-xyz-tob hyper-xyz-mbo

Seat expired or removed

Seats are monthly. If the invoice is not paid before expiry, the seat is removed and the tunnel will not stay up.

"Multicast user already exists"

You already have an active subscription through a different path. Disconnect first, then retry connect:

  • Edge Connect: docker exec doublezero-edge-connect doublezero disconnect
  • Native: doublezero disconnect

Then retry doublezero connect multicast --subscribe-feed <feed-code> on the same path (container or host).

AWS-specific

Disable the source/destination check on the instance’s ENI. Without this, GRE-encapsulated multicast may be dropped.