Skip to main content

Installing the Mainnet Node

Ensure the requirements listed in the following sections are met before you start setting up the Mainnet node.

Networking Requirements

The following ports are used by the node:

  • 35000 (required to be externally visible)
  • 7777 RPC endpoint for interaction with JSON-RPC API
  • 8888 REST endpoint for status and metrics (having this accessible allows your node to be part of network status)
  • 9999 SSE endpoint for event stream

Of these 35000 is the only port required to be open for your node to function, however, opening 8888 will allow others to know general network health.

OS Requirements

The recommended OS version is Ubuntu 20.04.

Number of Open Files

Please read through this page on nofiles configuration to put settings in /etc/security/limits.conf for your node to ensure proper operation.

Clean up Required

If you were running a previous node on this box, this will clean up state. If packages are not installed, the apt remove may give errors, but this is not a problem.

sudo systemctl stop casper-node-launcher.service
sudo apt remove -y casper-client
sudo apt remove -y casper-node
sudo apt remove -y casper-node-launcher
sudo rm /etc/casper/casper-node-launcher-state.toml
sudo rm -rf /etc/casper/1_*
sudo rm -rf /var/lib/casper/*

Setup CasperLabs Repo for Packages

The following commands will set up the CasperLabs repository for packages:

echo "deb" bionic main | sudo tee -a /etc/apt/sources.list.d/casper.list
curl -O
sudo apt-key add casper-repo-pubkey.asc
sudo apt update

Install casper-node-launcher, casper-client, and jq

sudo apt install -y casper-client casper-node-launcher jq

Install all Protocols

sudo -u casper /etc/casper/ stage_protocols casper.conf

Validator Keys

If you do not have keys, you can create them using the following command:

sudo -u casper casper-client keygen /etc/casper/validator_keys

Note: To avoid losing your keys if you lose machine data, save them offline.

Get a Trusted Hash

To get a trusted hash, use this command:

sudo sed -i "/trusted_hash =/c\trusted_hash = '$(casper-client get-block --node-address -b 20 | jq -r .result.block.hash | tr -d '\n')'" /etc/casper/1_0_0/config.toml

Note: If the IP address in the above command is not responding, you can find active peers at for the Mainnet. For the Testnet, you can find active peers at

Start the Node

Start the node using the following commands:

sudo /etc/casper/ rotate_logs
sudo /etc/casper/ start

Monitor the node syncing

The following command will display the node syncing details:

/etc/casper/ watch

When you run the watch command, expect to see something like this:

Last Block: 630151 (Era: 4153)
Peer Count: 297
Uptime: 4days 6h 40m 18s 553ms
Build: 1.4.5-a7f6a648d-casper-mainnet
Key: 0147b4cae09d64ab6acd02dd0868722be9a9bcc355c2fdff7c2c244cbfcd30f158
Next Upgrade: None

RPC: Ready

● casper-node-launcher.service - Casper Node Launcher
Loaded: loaded (/lib/systemd/system/casper-node-launcher.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2022-03-16 21:08:50 UTC; 4 days ago
Main PID: 2934 (casper-node-lau)
Tasks: 12 (limit: 4915)
CGroup: /system.slice/casper-node-launcher.service
├─ 2934 /usr/bin/casper-node-launcher
└─16842 /var/lib/casper/bin/1_4_5/casper-node validator /etc/casper/1_4_5/config.toml

If your casper-node-launcher status is not shown as active (running) with an increasing time, you are either not running or in the process of restarting.

Monitor your node once it is up

The community has created a few tools to monitor your node once it is running, such as: