RpcNode Toolkit

Home/Networks/Hyperliquid

hyperliquid

Hyperliquid full node

Self-host a Hyperliquid full node with the official snapshot and EVM RPC — one environment per server.

Install ToolkitOfficial docs

Client

Hyperliquid node (official binary)

RPC

EVM JSON-RPC after applied blocks (eth_* )

History

Full HL state after official snapshot. One environment per host.

Hyperliquid is a dedicated-host chain in Toolkit: one environment per machine. The catalog pin is a rolling CDN artifact (date + ETag), not a GitHub tag name.

Sync proof uses applied-block logs and eth_syncing before the node is called Synced. Operate visor.json and the node from the panel after start.

Environments

mainnettestnet

Install

  1. On Ubuntu 24.04 LTS:
    bash
    curl -fsSL "https://toolkit.rpcnode.dev/install/agent.sh" | sudo bash
    Supported and recommended: Ubuntu 24.04 LTS (amd64 or arm64). Other operating systems have not been tested.
  2. Panel → Add server (Agent URL + token) → Add node → Hyperliquid → mainnet.
  3. Confirm ports, choose install options if this chain has them, install Hyperliquid node (official binary), snapshot if required, start. Watch sync on the node page.

Operate from the panel

After the node is up you manage it in the same UI — Node Config (edit the live files and apply), client updates, restart, logs, public RPC. You do not need SSH to change conf. Install-time choices (snapshot flavor, history window, disk layout) are stored on that node.

FAQ

How do I run a Hyperliquid full node?
Install the host agent, add the server, then Add node → Hyperliquid. Toolkit provisions Hyperliquid node (official binary).
Can I change the Hyperliquid config later?
Yes. Node page → Node Config. Edit and apply; restart from the same page. A different snapshot or history flavor is an Install choice — changing it later usually means wipe and Add node again.
Pruned or light?
Full HL state after official snapshot. One environment per host.
Catalog
/clients/hyperliquid/ · catalog.json

Other networks