DVT Home Staking Curriculum

Nimbus BN

Download Nimbus

Download the latest version of Nimbus, extract the zipped file, and then run the checksum verification process to ensure that the "nimbus_beacon_node" and "nimbus_validator_client" files have not been tampered with during download.

cd
curl -LO https://github.com/status-im/nimbus-eth2/releases/download/v24.5.1/nimbus-eth2_Linux_amd64_24.5.1_d2a07514.tar.gz
tar xvf nimbus-eth2_Linux_amd64_24.5.1_d2a07514.tar.gz
cd nimbus-eth2_Linux_amd64_24.5.1_d2a07514/build
echo "4a8230a69089bbdcc7abc86f9471e034cfbd32344e9b01be85e88ed3b54d7cfb83abbf7b32aaf9c957eb4a762b0aa34e63b0ea47a3943bbd07aef8812777f7d7  nimbus_beacon_node" | sha512sum --check
echo "1d3a826d1e5e6be58070570efe594b012fd4fb68f3ae449c37aae956d1cf8664a5286b09cc1bd47f7bdff5c2b4af9e83d8a5d8d6fe1153c540023e5bbe2276e2  nimbus_validator_client" | sha512sum --check

Each downloadable file comes with it's own checksum. Replace the actual checksum and URL of the download link in the code block above.

Make sure to choose the amd64 version. Right click on the linked text and select "copy link address" to get the URL of the download link to curl.

Expected output: Verify output of the checksum verification.

nimbus_beacon_node: OK
nimbus_validator_client: OK

If checksum is verified, extract the consensus client and validator client binaries into the (/usr/local/bin) directory (as a best practice). Then, clean up the duplicated copies.

cd ~/nimbus-eth2_Linux_amd64_24.5.1_d2a07514/build
sudo cp nimbus_beacon_node nimbus_validator_client /usr/local/bin
cd
rm -r nimbus-eth2_Linux_amd64_24.5.1_d2a07514 nimbus-eth2_Linux_amd64_24.5.1_d2a07514.tar.gz

Configure the Nimbus Consensus Client

We will be running the Consensus client and Validator client of Nimbus as separate services so that there is more flexibility to configure a failover node for maximum uptime when you decide it is needed.

Create an account (nimbus) without server access for the Nimbus Beacon Node & Validator Client to run as a background service. This type of user account will not have root access so it restricts potential attackers to only the Nimbus Beacon Node & Validator Client services in the unlikely event that they manage to infiltrate via a compromised client update.

sudo useradd --no-create-home --shell /bin/false nimbus

Create a directory for Nimbus to store the blockchain and validator data of the Consensus layer. Move the validator_keys directory into this folder. Then set the owner of this directory to the Nimbus so that this user can read and write to the directory.

sudo mkdir -p /var/lib/nimbus_beacon
sudo chmod 700 /var/lib/nimbus_beacon

If there are no errors, create a systemd configuration file for the Nimbus Beacon Node service to run in the background.

sudo nano /etc/systemd/system/nimbusbeacon.service

Paste the configuration parameters below into the file:

[Unit]
Description=Nimbus Beacon Node (Holesky)
Wants=network-online.target
After=network-online.target

[Service]
User=nimbus
Group=nimbus
Type=simple
Restart=always
RestartSec=5
ExecStart=/usr/local/bin/nimbus_beacon_node \
  --network=holesky \
  --data-dir=/var/lib/nimbus_beacon \
  --web3-url=http://127.0.0.1:8551 \
  --jwt-secret=/var/lib/jwtsecret/jwt.hex \
  --payload-builder=true \
  --payload-builder-url=http://127.0.0.1:18550 \
  --tcp-port=9001 \
  --udp-port=9001 \
  --rest \
  --rest-address=<Internal_IP_address> \
  --rest-port=5051 \
  --metrics \
  --metrics-port=8009 
  
[Install]
WantedBy=multi-user.target

Once you're done, save with Ctrl+O and Enter, then exit with Ctrl+X. Understand and review your configuration summary below, and amend if needed.

Nimbus Beacon Node configuration summary:

  1. --network: Run the beacon node service on the ETH Holesky testnet

  2. --data-path: Specify the directory for Nimbus to store data related to the consensus client

  3. --web3-url: URL to connect to the execution layer client

  4. --jwt-secret: File path to locate the JWT secret we generated earlier

  5. --payload-builder: Enable external payload builder

  6. --payload-builder-url: URL to connect to external payload builder (MEV-boost)

  7. --tcp-port / --udp-port: Sets the port for peer-to-peer communication. Defaults to 9000.

  8. --rest: Enable the REST API endpoint for validator and DVT clients to connect to this consensus client

  9. --rest-address: Sets the IP address to connect to the REST API of the consensus client that will be used by the DVT clients. Use the internal IP address of your device here (check by running ip a) - e.g. 192.168.x.x. Defaults to 127.0.0.1 otherwise

  10. --rest-port: Port to connect to the REST API endpoint

  11. --metrics: Enable monitoring of consensus client metrics

  12. --metrics-port: Port to connect to the metrics endpoint

Run the checkpoint sync process

For Nimbus, you have to first run the checkpoint sync process separately before firing up the consensus client with the above configurations.

sudo /usr/local/bin/nimbus_beacon_node trustedNodeSync --network=holesky --data-dir=/var/lib/nimbus_beacon --trusted-node-url=https://holesky.beaconstate.ethstaker.cc/ --backfill=false

Expected output:

Start the Nimbus Consensus Client

First we have to change the owner of the nimbus beacon data directory to the nimbus user.

sudo chown -R nimbus:nimbus /var/lib/nimbus_beacon

Reload systemd to register the changes made, start the Nimbus Consensus Client service, and check its status to make sure its running.

sudo systemctl daemon-reload
sudo systemctl start nimbusbeacon.service
sudo systemctl status nimbusbeacon.service

Expected output: The output should say Nimbus Beacon Node is “active (running)”. Press CTRL-C to exit and Nimbus Beacon Node will continue to run. It should take just a few minutes for Nimbus to sync on the Holesky.

Use the following command to check the logs of Nimbus Consensus Client’s syncing process. Watch out for any warnings or errors.

sudo journalctl -fu nimbusbeacon -o cat | ccze -A

Expected output:

Press Ctrl+C to exit monitoring.

Note: You will see some warnings around "Block failed to load unexpectedly" if your execution client has yet to fully sync. The following output is expected initially and should go away after a few hours.

If the Nimbus Consensus Client service is running smoothly, we can now enable it to fire up automatically when rebooting the system.

sudo systemctl enable nimbusbeacon.service

Resources

PreviousTeku BNNextLodestar BN

Last updated