Client
Hyperliquid node (official binary)
hyperliquid
How to install Hyperliquid full node
Install Hyperliquid node (official binary) as a self-hosted Hyperliquid full node on your server. This guide covers the agent, network selection, setup, and sync.
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
How to install Hyperliquid node
Choose mainnet, testnet in Toolkit, then follow these steps to provision and run a Hyperliquid full node.
- Install the panel and host agent using the documentation, then register the server in the panel.
- In Add node, select Hyperliquid and the required environment.
- Review the network options, start provisioning, and follow sync status and logs from 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 install Hyperliquid full node?
- Install the host agent, add the server, then choose Hyperliquid and an environment in Add node. Toolkit provisions Hyperliquid node (official binary) and tracks sync from the panel.
- 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.