Updating your execution client
Scenario: In discord, you see an alert that your execution client just announced a new release. How best to update?
The following steps align with our mainnet guide. You may need to adjust file names and directory locations where appropriate. The core concepts remain the same.
From time to time, be sure to update to the latest ETH1 releases to enjoy new improvements and features.
0.1 Update your operating system and ensure it's on the latest long term (LTS) support version.
sudo apt update
sudo apt dist-upgrade -y
1. Stop your execution client process.
# This can take a few minutes.
sudo systemctl stop eth1
2. Update the execution client package or binaries.
# Already handled by previous commands.
# sudo apt update
# sudo apt upgrade -y
As of Feb 17, 2023, Besu requires minimum Java 17 and up to build and run.
Run the following to update to Java 17.
#Install Java 17
sudo apt install openjdk-17-jre
#Verify Java 17 is installed
Run the following to automatically download the latest linux release, un-tar and cleanup.
BINARIES_URL="$(curl -s https://api.github.com/repos/hyperledger/besu/releases/latest | grep -o 'https://hyperledger.jfrog.io/hyperledger/besu-binaries/besu/.*tar.gz' | sed -e 's/.*\\n\(https.*.tar.gz$\)/\1/')"
echo Downloading URL: $BINARIES_URL
# backup previous besu version in case of rollback
mv besu besu_backup_$(date +"%Y%d%m-%H%M%S")
# download latest besu
wget -O besu.tar.gz "$BINARIES_URL"
tar -xvf besu.tar.gz
# rename besu to standard folder location
mv besu-* besu
Automatically download the latest linux release, un-zip and cleanup.
# backup previous nethermind version in case of rollback
mv nethermind nethermind_backup_$(date +"%Y%d%m-%H%M%S")
# store new version in nethermind directory
mkdir nethermind && cd nethermind
# download latest version
curl -s https://api.github.com/repos/NethermindEth/nethermind/releases/latest | jq -r ".assets | select(.name) | .browser_download_url" | grep linux-x64 | xargs wget -q --show-progress
unzip -o nethermind*.zip
3. Start your execution client process.
sudo systemctl start eth1
4. Check the logs to verify the services are working properly and ensure there are no errors.
Lighthouse | Prysm | Lodestar
Nimbus | Teku
sudo systemctl status eth1 beacon-chain validator
sudo systemctl status eth1 beacon-chain
5. Finally, verify your validator's attestations are working with public block explorer such as
Enter your validator's pubkey to view its status.
Last modified 3mo ago