Maintenance guide for Gnosis staking

Maintenance guide for Gnosis staking.

As a regular member securying the network and processing blockchain operations on it, you need to keep your software up to date to avoid penalties and earning rewards for the processed work.

You can check current versions of individual clients at clients page.

Disclaimer

This guide is for informational purposes only. The author nor website owner does not guarantee accuracy of the information in this guide and is not responsible for any damages or losses incurred by following the guide.

Updating OS

Be sure your Operating system is up to date.

sudo apt update && sudo apt -y upgrade

sudo apt dist-upgrade && sudo apt autoremove

Updating Staking clients

Execution Client
Updating Nethermind client

Nethermind documentation: https://docs.nethermind.io/

Check current version of Nethermind running on the server
```
$ /usr/local/bin/nethermind/./nethermind-cli --version
```
1. Find the latest stable version of Nethermind on Github
  - Find latest Nethermind version at https://github.com/NethermindEth/nethermind/releases
  - Write latest stable Nethermind version in format such as 1.31.6-4e68f8ee:
2. Download Nethermind version 1.31.6-4e68f8ee to your node
```
cd ~/downloads && curl -LO https://github.com/NethermindEth/nethermind/releases/download/1.31.6/nethermind-1.31.6-4e68f8ee-linux-x64.zip
```
3. Unzip the downloaded file
```
unzip nethermind-1.31.6-4e68f8ee-linux-x64 -d nethermind
```
4. Stop running clients
  $ journalctl -fu nethermind
  
  $ sudo systemctl stop nethermind && systemctl status nethermind
  
  /usr/local/bin/staking.sh monitor execution
  
  /usr/local/bin/staking.sh stop execution && /usr/local/bin/staking.sh check execution
5. Remove the old client
```
sudo rm -r /usr/local/bin/nethermind
```
6. Copy the client to /usr/local/bin/
```
sudo cp -a nethermind /usr/local/bin/nethermind
```
7. Start the client again
  $ sudo systemctl start nethermind && systemctl status nethermind
  
  $ journalctl -fu nethermind
  
  /usr/local/bin/staking.sh start execution && /usr/local/bin/staking.sh check execution
  
  /usr/local/bin/staking.sh monitor execution
8. Remove downloaded files
```
cd ~/downloads && rm nethermind-1.31.6-4e68f8ee-linux-x64.zip && rm -r nethermind
```
Updating Erigon client

Erigon documentation: https://erigon.gitbook.io/erigon

Check current version of Erigon running on the server:
```
$ /usr/local/bin/erigonlib/erigon -v
```
1. Find the latest stable version of Erigon on Github
  - Find latest Erigon version at https://github.com/ledgerwatch/erigon/releases. AMD64 v1/v2 links at Microarchitecture levels.
  - Write latest stable Erigon version:
2. Download Erigon version 3.0.0
```
cd ~/downloads && curl -LO https://github.com/erigontech/erigon/releases/download/v3.0.0/erigon_v3.0.0_linux_amd64v2.tar.gz
```
3. Verify hash of donwnloaded file
  Get hash of downloaded file and compare it with official hashes
```
sha256sum erigon_v3.0.0_linux_amd64v2.tar.gz
```
  And check it compare to the provided hash for the file from https://github.com/erigontech/erigon/releases/download/v3.0.0/erigon_v3.0.0_checksums.txt (Note: The link links at 3.0.0 version )
4. Extract the downloaded package
```
tar xvf erigon_v3.0.0_linux_amd64v2.tar.gz
```
5. Stop Erigon client
  Note: It's a good practice to check the log before stopping the client. journalctl -fu erigon
  
  sudo systemctl stop erigon && systemctl status erigon
  
  Note: It's a good practice to check the log before stopping the client. /usr/local/bin/staking.sh monitor execution
  
  /usr/local/bin/staking.sh stop execution && /usr/local/bin/staking.sh check execution
6. Remove old library
```
sudo rm -r /usr/local/bin/erigonlib
```
7. Copy extracted Erigon library
```
sudo cp -a erigon_v3.0.0_linux_amd64v2 /usr/local/bin/erigonlib
```
8. Start Erigon client and check its status
  sudo systemctl start erigon && systemctl status erigon
  
  /usr/local/bin/staking.sh start execution && /usr/local/bin/staking.sh check execution
9. Monitor Erigon client
  journalctl -fu erigon
  
  /usr/local/bin/staking.sh monitor execution
10. Remove downloaded files
```
cd ~/downloads && rm -r erigon_v3.0.0_linux_amd64v2.tar.gz && rm -r erigon_v3.0.0_linux_amd64v2
```
Soon

Soon
Consensus clients (Beacon and Validator(s))
Check current version of Lighthouse running on the server:
lighthouse --version
curl "http://127.0.0.1:5052/eth/v1/node/version"
1. Find the latest stable version of Lighthouse on Github
  - Find latest Lighthouse version at https://github.com/sigp/lighthouse/releases
  - Write latest stable lighthouse version:
    
    This will update the url links in the guide below.
2. Download Lighthouse version 6.0.1 to your node
```
cd ~/downloads && curl -LO https://github.com/sigp/lighthouse/releases/download/v6.0.1/lighthouse-v6.0.1-x86_64-unknown-linux-gnu.tar.gz
```
  Extract downloaded file
```
$ tar xvf lighthouse-v6.0.1-x86_64-unknown-linux-gnu.tar.gz
```
3. Stop Lighthouuse services
  Stop Lighthouse Beacon service and all validators-based services
  
  sudo systemctl stop gno-lighthousebeacon sudo systemctl stop gno-lighthouse-vi... sudo systemctl stop gno-lighthouse-vi... ...
  
  This option requires installed and configured Staking manager
  
  Stop cosnsensus services
  
  /usr/local/bin/staking.sh stop consensus
  
  Check cosnsensus services status
  
  /usr/local/bin/staking.sh check consensus
4. Replace old Lighthouse client for new
```
$ sudo cp ~/downloads/lighthouse /usr/local/bin
```
5. Start the Lighthouse services
  Start Lighthouse Beacon service and all validators-based services
  
  sudo systemctl start gno-lighthousebeacon sudo systemctl start gno-lighthouse-vi... sudo systemctl start gno-lighthouse-vi... ...
  
  This option requires installed and configured Staking manager
  
  /usr/local/bin/staking.sh start consensus
6. Monitor
  systemctl status gno-lighthousebeacon gno-lighthouse-vi.. gno-lighthouse-vi..
  
  journalctl -fu gno-lighthousebeacon
  
  journalctl -f -u gno-lighthouse-vi.. -u gno-lighthouse-vi...
  
  This option requires installed and configured Staking manager
  
  /usr/local/bin/staking.sh check consensus
  
  /usr/local/bin/staking.sh monitor consensus
7. Remove downloaded files
```
$ cd ~/downloads && rm lighthouse-v6.0.1-x86_64-unknown-linux-gnu.tar.gz && rm -r lighthouse
```
Check current version of Lodestar running on the server:
```
cd /usr/local/bin/lodestar && ./lodestar -v
```
1. Get Lodestar Client
  Remove old client folder
  
  cd ~/downloads && sudo rm -r lodestarclient && sudo rm -r lodestar
  
  Find the latest stable version of Lodestar client on Github
  
  Find latest Lodestar version at https://github.com/ChainSafe/lodestar/releases
  
  Write latest stable Lodestar version:
  
  This will update the url links in the guide below.
  
  Download Lodestar version 1.28.1 to your node
  
  mkdir ~/downloads/lodestarclient && cd ~/downloads/lodestarclient && curl -LO https://github.com/ChainSafe/lodestar/releases/download/v1.28.1/lodestar-v1.28.1-linux-amd64.tar.gz
  
  Extract downloaded file
  
  $ tar xvf lodestar-v1.28.1-linux-amd64.tar.gz
  
  Create lodestar directory and move the client into it
  
  mkdir ~/downloads/lodestar && mv ~/downloads/lodestarclient/lodestar ~/downloads/lodestar/lodestar
  
  Remove old repository clone
  
  cd ~/downloads && sudo rm -r lodestar
  
  Build Lodestar
  
  Download latest Lodestar client from GitHub
  cd ~/downloads && git clone -b stable https://github.com/chainsafe/lodestar.git
  
  Install yarn
  cd lodestar && yarn install
  
  Build Lodestart client
  yarn run build
2. Check version of new Lodestar client
```
~/downloads/lodestar/lodestar -v
```
3. Stop Lodestar services
  Stop Lodestar Beacon service and all validators-based services
  
  sudo systemctl stop gno-lodestarbeacon sudo systemctl stop gno-lodestar-vi... sudo systemctl stop gno-lodestar-vi... ...
  
  This option requires installed and configured Staking manager
  
  Stop cosnsensus services
  
  /usr/local/bin/staking.sh stop consensus
  
  Check cosnsensus services status
  
  /usr/local/bin/staking.sh check consensus
4. Remove old production Lodestar client
```
sudo rm -r /usr/local/bin/lodestar
```
5. Copy new production client to /usr/local/bin directory
```
sudo cp -a ~/downloads/lodestar /usr/local/bin
```
6. Start the Lodestar services
  Start Lodestar Beacon service and all validators-based services
  
  sudo systemctl start gno-lodestarbeacon sudo systemctl start gno-lodestar-vi... sudo systemctl start gno-lodestar-vi... ...
  
  This option requires installed and configured Staking manager
  
  /usr/local/bin/staking.sh start consensus
7. Monitor
  systemctl status gno-lodestarbeacon gno-lodestar-vi.. gno-lodestar-vi..
  
  journalctl -fu gno-lodestarbeacon
  
  journalctl -f -u lodestar-vi.. -u lodestar-vi..
  
  This option requires installed and configured Staking manager
  
  /usr/local/bin/staking.sh check consensus
  
  /usr/local/bin/staking.sh monitor consensus
Check current version of Teku running on the server:
```
/usr/local/bin/teku/bin/teku --version
```
1. Find the latest stable version of Teku on Github
  Find latest Teku version at Github: https://github.com/Consensys/teku/releases
  Write latest stable Teku version:
  
  This will update the url links in the guide below.
2. Download the latest Teku version
```
cd ~/downloads && curl -LO https://artifacts.consensys.net/public/teku/raw/names/teku.tar.gz/versions/25.3.0/teku-25.3.0.tar.gz
```
3. Unpack the downloaded Teku version
```
$ tar xvf teku-25.3.0.tar.gz
```
4. Stop Teku services
  Stop Teku Beacon service and all validators-based services
  
  sudo systemctl stop gno-tekubeacon sudo systemctl stop gno-teku-vi... sudo systemctl stop gno-teku-vi... ...
  
  Check services status for state
  
  sudo systemctl status gno-tekubeacon sudo systemctl status gno-teku-vi...; sudo systemctl status gno-teku-vi... ...
  
  This option requires installed and configured Staking manager
  
  Stop cosnsensus services
  
  /usr/local/bin/staking.sh stop consensus
  
  Check cosnsensus services status
  
  /usr/local/bin/staking.sh check consensus
5. Remove Old Teku Library
```
sudo rm -r /usr/local/bin/teku
```
6. Copy the Teku Library
```
sudo cp -a ~/downloads/teku-25.3.0 /usr/local/bin/teku
```
7. Start the services again
  Start Teku Beacon service and all validators-based services
  
  sudo systemctl start gno-tekubeacon sudo systemctl start gno-teku-vi... sudo systemctl start gno-teku-vi... ...
  
  This option requires installed and configured Staking manager
  
  /usr/local/bin/staking.sh start consensus
8. Monitor
  systemctl status gno-tekubeacon gno-teku-vi..
  
  journalctl -fu gno-tekubeacon
  
  journalctl -f -u teku-vi.. -u teku-vi..
  
  This option requires installed and configured Staking manager
  
  /usr/local/bin/staking.sh check consensus
  
  /usr/local/bin/staking.sh monitor consensus
9. Remove downloaded files
```
cd ~/downloads && rm teku-25.3.0.tar.gz && rm -r teku-25.3.0
```
Guide under construction, not tested yet. Do not use it for production.

Check current version of Nimbus running on the server:
```
cd /usr/local/bin
```
Beacon chain
```
./nimbus-beacon --version
```
Validator:
```
./nimbus-validator --version
```
Find the latest stable version of Nimbus on Github
Find latest Nimbus version at Github: https://github.com/status-im/nimbus-eth2/releases
Write latest stable Nimbus version:

This will update the url links in the guide below.

Download the latest Nimbus client

cd ~/downloads && curl -LO https://github.com/status-im/nimbus-eth2/releases/download/v25.2.0/nimbus-eth2_Linux_amd64_25.2.0_c6688004.tar.gz

Extract the downloaded package

tar xvf nimbus-eth2_Linux_amd64_25.2.0_c6688004.tar.gz

Stop Nimbus services

Stop Nimbus Beacon service and all validators-based services

sudo systemctl stop gno-nimbusbeacon sudo systemctl stop gno-nimbus-vi... sudo systemctl stop gno-nimbus-vi... ...

Check services status for state

sudo systemctl status gno-nimbusbeacon sudo systemctl status gno-nimbus-vi...; sudo systemctl status gno-nimbus-vi... ...

This option requires installed and configured Staking manager

Stop cosnsensus services

/usr/local/bin/staking.sh stop consensus

Check cosnsensus services status

/usr/local/bin/staking.sh check consensus

Copy Nimbus clients to /usr/local/bin

sudo cp -a nimbus-eth2_Linux_amd64_25.2.0_c6688004/build /usr/local/bin/nimbus

Start the services again

Start Nimbus Beacon service and all validators-based services

sudo systemctl start gno-nimbusbeacon sudo systemctl start gno-nimbus-vi... sudo systemctl start gno-nimbus-vi... ...

This option requires installed and configured Staking manager

/usr/local/bin/staking.sh start consensus

Monitor

systemctl status gno-nimbusbeacon gno-nimbus-vi..

journalctl -fu gno-nimbusbeacon

journalctl -f -u nimbus-vi.. -u nimbus-vi..

This option requires installed and configured Staking manager

/usr/local/bin/staking.sh check consensus

/usr/local/bin/staking.sh monitor consensus

Remove downloaded files

rm nimbus-eth2_Linux_amd64_25.2.0_c6688004.tar.gz && rm -r nimbus-eth2_Linux_amd64_25.2.0_c6688004
Download the latest Nimbus client

cd ~/downloads && git clone -b stable https://github.com/status-im/nimbus-eth2.git

Move update

cd nimbus-eth2 && make update

Build Nimbus

make gnosis-build

make gnosis-vc-build

Copy Nimbus clients to /usr/local/bin

sudo cp -a build /usr/local/bin/nimbus
Check current version of Prysm running on the server:
```
cd /usr/local/bin
```
Beacon chain:
```
./beacon-chain --version
```
Validator:
```
./validator --version
```
1. Find the latest stable version of Prysm on Github
  - Find latest Prysm version at https://github.com/prysmaticlabs/prysm/releases
  - Write latest stable Prysm version:
    
    This will update the url links in the guide below.
2. Download Prysm clients to your node
```
cd ~/downloads && curl -LO https://github.com/prysmaticlabs/prysm/releases/download/v5.3.1/beacon-chain-v5.3.1-modern-linux-amd64
```
```
cd ~/downloads && curl -LO https://github.com/prysmaticlabs/prysm/releases/download/v5.3.1/validator-v5.3.1-linux-amd64
```
3. Rename downloaded files
```
mv beacon-chain-v5.3.1-modern-linux-amd64 beacon-chain && mv validator-v5.3.1-linux-amd64 validator
```
4. Set files permissions
```
chmod +x beacon-chain && chmod +x validator
```
5. Stop running clients
  
  You can time this based on validator duties either from validator instances log(s) or for Ethereum also from sources such as WenMerge.com or ETHStakers.
  // Stop all validator instances using Prysm clients on all chains // sudo systemctl stop prysmvalidator1 // sudo systemctl stop prysmvalidator2 // sudo systemctl stop prysmRocketpoolValidator // sudo systemctl stop prysmStakewiseValidator // ... // Stop beaconchain clients using PrysmBeacon client on all chains sudo systemctl stop prysmbeacon
  
  NOTE: This section uses Staking manager script.
  
  /usr/local/bin/staking.sh stop consensus
  
  Check the services
  
  /usr/local/bin/staking.sh check
6. Copy clients to /usr/local/bin
```
sudo cp ~/downloads/beacon-chain /usr/local/bin
```
```
sudo cp ~/downloads/validator /usr/local/bin
```
7. Start services using Prysm clients
  // Start all validator instances using Prysm clients on all chains // sudo systemctl start prysmvalidator1 // sudo systemctl start prysmvalidator2 // sudo systemctl start prysmRocketpoolValidator // sudo systemctl start prysmStakewiseValidator // ... // Start beaconchain clients using PrysmBeacon client on all chains sudo systemctl start prysmbeacon
  
  NOTE: This section uses Staking manager script.
  
  /usr/local/bin/staking.sh start consensus
  
  Check the services status
  
  /usr/local/bin/staking.sh check
8. Monitor
  journalctl -fu prysmbeacon.service
  
  journalctl -f -u prysmvalidator.service -u prysmvalidator2.service
  
  ...
  
  This option requires installed and configured Staking manager
  
  /usr/local/bin/staking.sh check consensus
  
  /usr/local/bin/staking.sh monitor consensus
9. Remove downloaded files
```
cd ~/downloads && rm beacon-chain && rm validator
```
Updating MEV client (if used)
Check current version: /usr/local/bin/mev-boost --version
- Find the latest stable version at Github
  
  Write latest stable Mev-boost version from https://github.com/flashbots/mev-boost/releases:
- Download Mev-boost version 1.8 from GitHub
```
cd ~/downloads
curl -LO https://github.com/flashbots/mev-boost/releases/download/v1.8/mev-boost_1.8_linux_amd64.tar.gz
```
  Get hash of the downloaded file
```
sha256sum mev-boost_1.8_linux_amd64.tar.gz
```
  And compare it to content of https://github.com/flashbots/mev-boost/releases/download/v1.8/checksums.txt.
- Unpack mevboost
```
tar xvf mev-boost_1.8_linux_amd64.tar.gz
```
  Remove downloaded + useless unpacked files
```
rm LICENSE README.md mev-boost_1.8_linux_amd64.tar.gz
```
- Stop mevboost client
```
sudo systemctl stop mevboost
```
- Rewrite original mev-boost client
```
sudo cp ~/downloads/mev-boost /usr/local/bin
```
- Start Mev boost service
```
sudo systemctl start mevboost
```
- Monitor Mev-boost running
```
systemctl status mevboost
```
```
journalctl -fu mevboost.service
```
Updating service(s) client(s) (if used)

If you validate with services such as StakeWise, Rocketpool or Lido, be sure that also these clients are up to date.

Maintenance guide for Gnosis staking

Disclaimer

Updating OS

Updating Staking clients

Execution Client

Updating Nethermind client

Check current version of Nethermind running on the server

Find the latest stable version of Nethermind on Github

Download Nethermind version 1.31.6-4e68f8ee to your node

Unzip the downloaded file

Stop running clients

Remove the old client

Copy the client to /usr/local/bin/

Start the client again

Remove downloaded files

Updating Erigon client

Check current version of Erigon running on the server:

Find the latest stable version of Erigon on Github

Download Erigon version 3.0.0

Verify hash of donwnloaded file

Extract the downloaded package

Stop Erigon client

Remove old library

Copy extracted Erigon library

Start Erigon client and check its status

Monitor Erigon client

Remove downloaded files

Consensus clients (Beacon and Validator(s))

Check current version of Lighthouse running on the server:

Find the latest stable version of Lighthouse on Github

Download Lighthouse version 6.0.1 to your node

Stop Lighthouuse services

Start the Lighthouse services

Monitor

Check current version of Lodestar running on the server:

Get Lodestar Client

Remove old client folder

Find the latest stable version of Lodestar client on Github

Download Lodestar version 1.28.1 to your node

Extract downloaded file

Create lodestar directory and move the client into it

Remove old repository clone

Build Lodestar

Check version of new Lodestar client

Stop Lodestar services

Remove old production Lodestar client

Copy new production client to /usr/local/bin directory

Start the Lodestar services

Monitor

Check current version of Teku running on the server:

Find the latest stable version of Teku on Github

Download the latest Teku version

Unpack the downloaded Teku version

Stop Teku services

Remove Old Teku Library

Copy the Teku Library

Start the services again

Monitor

Remove downloaded files

Check current version of Nimbus running on the server:

Find the latest stable version of Nimbus on Github

Download the latest Nimbus client

Extract the downloaded package

Stop Nimbus services

Copy Nimbus clients to /usr/local/bin

Start the services again

Monitor

Remove downloaded files

Download the latest Nimbus client

Move update

Build Nimbus

Copy Nimbus clients to /usr/local/bin

Check current version of Prysm running on the server:

Find the latest stable version of Prysm on Github

Download Prysm clients to your node

Rename downloaded files

Set files permissions

Stop running clients

Copy clients to /usr/local/bin

Start services using Prysm clients

Download Nethermind version `1.31.6-4e68f8ee` to your node

Copy the client to `/usr/local/bin/`

Download Erigon version `3.0.0`

Download Lighthouse version `6.0.1` to your node

Download Lodestar version `1.28.1` to your node

Copy new production client to `/usr/local/bin` directory

Copy Nimbus clients to `/usr/local/bin`

Copy Nimbus clients to `/usr/local/bin`

Copy clients to `/usr/local/bin`

Download Mev-boost version `1.8` from GitHub