🦏
ETH Home Staking Collection
DVT Home Staking Curriculum
DVT Home Staking Curriculum
  • The DVT Home Staking Curriculum
  • Curriculum breakdown & timeline
  • Understanding ETH validators
    • Introduction to ETH Validators
    • Roles & Responsibilities of a node operator
    • Rewards and penalties
    • Importance of client diversity
    • Distributed Validator Technologies (DVTs)
    • Economics of using DVTs (WIP)
      • Diva Staking (WIP)
      • Obol (WIP)
      • SSV (WIP)
    • Bonded Validators
    • Economics of bonded validators (WIP)
  • Hardware & systems setup
    • Setup Overview
    • Hardware & system requirements
    • Procuring your hardware
    • Assemble your hardware
    • Practicing for free on Cloud VMs
      • Google Cloud
      • Alibaba Cloud
  • Linux OS, Networking, & Security
    • Install and prepare the OS
    • Networking & network security
    • Device level security setup
    • Verifying checksums
  • Installing & configuring your EL+CL clients
    • Set up and configure execution layer client
      • Nethermind
      • Besu
      • Geth
      • Erigon
      • Reth
    • Set up and configure consensus layer client
      • Teku BN
      • Nimbus BN
      • Lodestar BN
      • Lighthouse BN
      • Prysm BN
  • Keystore generation & MEV-Boost
    • Validator key generation
    • Set up and configure MEV-boost
  • Native Solo Staking Setup
    • Validator client setup
      • Teku VC
      • Nimbus VC
      • Lodestar VC
      • Lighthouse VC
      • Prysm VC
    • Depositing 32 ETH into your validator
    • Exiting your validator
  • Monitoring, Maintenance, and Updates
    • Set up monitoring suite
      • Installing & configuring Prometheus
      • Installing & configuring Node Exporter
      • Installing & configuring Grafana
      • Beaconcha.in App API
      • Client Uptime Check
    • Maintenance & Updates
      • Nethermind
      • Besu
      • Teku
      • Nimbus
      • Lodestar
      • Updating the monitoring suite
      • Preparing for Pectra
  • DVT Setup
    • Diva Staking
      • Diva Staking client setup
        • Default - All-in-one setup
        • Advanced - with standalone Lodestar VC
      • Registering your Diva node
      • Updating your Diva client
      • Monitoring your Diva Node
    • Obol
      • Techne Bronze Speedrun (Launchpad)
      • Obol + Bonded Validators (Techne Silver)
        • Obol + Lido CSM
    • SSV
      • SSV + Lido CSM (WIP)
      • SSV Operator
      • SSV Staker
  • Bonded Validators Setup
    • Lido CSM
      • Generating CSM keystores
      • Set Fee Recipient Address
        • Method 1: Configure on validator keys
        • Method 2: Configure on separate validator client
        • Verifying Fee Recipient Registered on MEV Relays
      • Upload/Remove/View validator keys
      • Rewards & bonds
      • Exiting CSM validators
        • "Lazy" exits (TESTNET ONLY)
        • Proper Exits
      • Role/Address management
      • Monitoring
      • Automations
        • CSM with ETHPillar
        • CSM with ETH Docker
        • CSM with Dappnode
    • Puffer
      • Non-Enclave: 2 ETH
    • Ether.fi
      • Receive distributed validator keyshares
    • Stader (WIP)
    • Rocketpool (WIP)
  • Liquid Staking Vaults
    • Stakewise V3
  • Mainnet
    • Mainnet Deployment
    • Heroglpyhs (WIP)
  • Best practices
    • Slashing prevention
    • Maximising uptime and performance
    • Optimising security
    • Managing your withdrawal wallet
  • Tips
    • Advanced networking
    • Downloading files from your node
  • Useful resources
    • General resources
    • Holesky Faucets
  • Automation/tools
    • ETHPillar
    • ETH Docker
    • Automated power on/off
      • Wake-on-LAN (WoL)
      • Network UPS Tools (NUT)
    • Validator Healthcheck Alerts
  • Solo Stakers Guild
    • Lido CSM+SSV+Obol (Testnet)
Powered by GitBook
On this page
  • Updating Nimbus
  • Download Nimbus
  • Restart the Nimbus services
  • Pruning Nimbus
  1. Monitoring, Maintenance, and Updates
  2. Maintenance & Updates

Nimbus

PreviousTekuNextLodestar

Last updated 1 year ago

Updating Nimbus

Download Nimbus

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.2.2/nimbus-eth2_Linux_amd64_24.2.2_fc9c72f0.tar.gz
tar xvf nimbus-eth2_Linux_amd64_24.2.2_fc9c72f0.tar.gz
cd nimbus-eth2_Linux_amd64_24.2.2_fc9c72f0/build
echo "ad062a475edbabb79882a85e1ba93d739d6614fdece382b65381211d07b9dc11487aedca15df0d540ba384866ed0ff0044989ce8d7c39054b2cad40d92022719 nimbus_beacon_node" | sha512sum --check
echo "1a5bfc3e5ba6e8b682572b8c7f74894b785191a4ba1ebf3d59203dc9dc1ec47b49c4d128aa433b0b44315ac574cbb7d924ab4241d60e2b9b141c61e504ab8dab  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.2.2_fc9c72f0/build
sudo cp nimbus_beacon_node nimbus_validator_client /usr/local/bin
cd
rm -r nimbus-eth2_Linux_amd64_24.2.2_fc9c72f0 nimbus-eth2_Linux_amd64_24.2.2_fc9c72f0.tar.gz

Restart the Nimbus services

sudo systemctl start nimbusbeacon.service nimbusvalidator.service
sudo systemctl status nimbusbeacon.service nimbusvalidator.service

Monitor journal logs using

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

Pruning Nimbus

Consensus clients take up a small amount of disk space when compared to execution clients. However, you can still free up ~200GB by pruning it if your validator node has been running for a while.

To prune consensus clients, simply delete the existing database and restart the beacon service with checkpoint sync enabled.

sudo systemctl stop nimbusbeacon.service
sudo rm -r /var/lib/nimbus_beacon/*
sudo systemctl start nimbusbeacon.service
sudo systemctl status nimbusbeacon.service

Monitor logs for errors.

sudo journalctl -fu tekubeacon -o cat | ccze -A
Download