Guide on how to setup a Hoodi testnet node (Reth/Lodestar)

Hoodi is a new Ethereum testnet meant to replace Holesky as a staking, infrastructure and protocol-developer testnet.

This guide is meant for people with little or some experience in running Ethereum clients and using the command-line interface (CLI). It will show you step by step how to setup your machine to join the Hoodi testnet by giving you the instructions to install and configure all the tools needed. It will assume you are using a modern linux distribution with systemd and APT (like Ubuntu 24.04 or Debian 12) on a modern x86 CPU (Intel, AMD). A clean install of your operating system on a dedicated machine or a virtual machine before proceeding is preferable.

Overview

We will use the latest version for Reth and the latest version for Lodestar. We will configure them to connect to the Hoodi testnet.

Executing the commands

Almost all of these commands will be performed in a terminal. Start your Terminal application. Any line that starts with the dollar sign ($) is a command that need to be executed in your terminal. Do not input the dollar sign ($) in your terminal, only the text that comes after that.

Executing a command with sudo will occasionally ask you for your password. Make sure to enter your account password correctly. You can execute the command again if you fail to enter the correct password after a few attempts.

Installing Prerequisites

Make sure we have fully updated packages first.

$ sudo apt -y update
$ sudo apt -y upgrade

Install prerequisites commonly available.

$ sudo apt -y install wget curl ccze

Installing Reth

Download the latest release version for Reth and extract it. If the latest version is more recent than what is used here, use that version and adjust for the new URL and archive name. Make sure to use the linux x86_64 version.

$ cd ~
$ wget https://github.com/paradigmxyz/reth/releases/download/v1.3.12/reth-v1.3.12-x86_64-unknown-linux-gnu.tar.gz
$ tar xvf reth-v1.3.12-x86_64-unknown-linux-gnu.tar.gz
$ rm reth-v1.3.12-x86_64-unknown-linux-gnu.tar.gz

Install this Reth version globally.

$ sudo cp ~/reth /usr/local/bin
$ rm ~/reth

Installing Lodestar

Download the latest release version for Lodestar and extract it. If the latest version is more recent than what is used here, use that version and adjust for the new URL and archive name. Make sure to use the linux amd64 version.

$ cd ~
$ wget https://github.com/ChainSafe/lodestar/releases/download/v1.29.0-rc.2/lodestar-v1.29.0-rc.2-linux-amd64.tar.gz
$ tar xvf lodestar-v1.29.0-rc.2-linux-amd64.tar.gz
$ rm lodestar-v1.29.0-rc.2-linux-amd64.tar.gz

Install this Lodestar version globally.

$ sudo cp ~/lodestar /usr/local/bin
$ rm ~/lodestar

Creating the JWT token file

Create a JWT token file in a neutral location and make it readable to everyone. We will use the /var/lib/ethereum/jwttoken location to store the JWT token file.

$ sudo mkdir -p /var/lib/ethereum
$ openssl rand -hex 32 | tr -d "\n" | sudo tee /var/lib/ethereum/jwttoken
$ sudo chmod +r /var/lib/ethereum/jwttoken

Configuring your Reth node

Create a dedicated user for running Reth, create a directory for holding the data and assign the proper permissions.

$ sudo useradd --no-create-home --shell /bin/false reth
$ sudo mkdir -p /var/lib/reth/logs
$ sudo chown -R reth:reth /var/lib/reth

Create a systemd service config file to configure the Reth node service.

$ sudo nano /etc/systemd/system/reth.service

Paste the following service configuration into the file. Exit and save once done (Ctrl + X, Y, Enter).

[Unit]
Description=Reth Execution Client (Hoodi)
After=network.target
Wants=network.target

[Service]
User=reth
Group=reth
Type=simple
Restart=always
RestartSec=5
TimeoutStopSec=180
ExecStart=reth node \
  --full \
  --chain hoodi \
  --datadir /var/lib/reth \
  --log.file.directory /var/lib/reth/logs \
  --metrics 6061 \
  --authrpc.jwtsecret /var/lib/ethereum/jwttoken

[Install]
WantedBy=default.target

Reload systemd to reflect the changes and start the service. Check status to make sure it’s running correctly.

$ sudo systemctl daemon-reload
$ sudo systemctl start reth.service
$ sudo systemctl status reth.service

It should say active (running) in green text. If not then go back and repeat the steps to fix the problem. Press Q to quit (will not affect the reth service).

Enable the reth service to automatically start on reboot.

$ sudo systemctl enable reth.service

You can watch the live messages from your Reth node logs using this command. Make sure nothing suspicious shows up in your logs.

$ sudo journalctl -f -u reth.service -o cat | ccze -A

Press Ctrl + C to stop showing those messages.

Configuring your Lodestar beacon node

Create a dedicated user for running the Lodestar beacon node, create a directory for holding the data, copy testnet files and assign the proper permissions.

$ sudo useradd --no-create-home --shell /bin/false lodestarbeacon
$ sudo mkdir -p /var/lib/lodestar
$ sudo chown -R lodestarbeacon:lodestarbeacon /var/lib/lodestar

Create a systemd service config file to configure the Lodestar beacon node service.

$ sudo nano /etc/systemd/system/lodestarbeacon.service

Paste the following service configuration into the file. Exit and save once done (Ctrl + X, Y, Enter).

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

[Service]
Type=simple
User=lodestarbeacon
Group=lodestarbeacon
Restart=always
RestartSec=5
ExecStart=lodestar beacon \
    --network hoodi \
    --dataDir /var/lib/lodestar \
    --checkpointSyncUrl https://hoodi.beaconstate.ethstaker.cc \
    --metrics \
    --metrics.port 6071 \
    --jwtSecret /var/lib/ethereum/jwttoken

[Install]
WantedBy=multi-user.target

Reload systemd to reflect the changes and start the service. Check status to make sure it’s running correctly.

$ sudo systemctl daemon-reload
$ sudo systemctl start lodestarbeacon.service
$ sudo systemctl status lodestarbeacon.service

It should say active (running) in green text. If not then go back and repeat the steps to fix the problem. Press Q to quit (will not affect the Lodestar beacon node service).

Enable the Lodestar beacon node service to automatically start on reboot.

$ sudo systemctl enable lodestarbeacon.service

You can watch the live messages from your Lodestar beacon node logs using this command. Make sure nothing suspicious shows up in your logs.

$ sudo journalctl -f -u lodestarbeacon.service -o cat | ccze -A

Press Ctrl + C to stop showing those messages.

Trying the Hoodi testnet

Requesting testnet funds

Requesting or obtaining enough Hoodi ETH to perform your validator deposit can be challenging. We suggest you use the EthStaker #cheap-hoodi-validator free process. Join the EthStaker Discord server and use the /cheap-hoodi-deposit slash command (start typing the command and it will show up above your input box). From there, follow the instructions from the bot. As an alternative, you can try obtaining 32 Hoodi ETH from this great faucet on https://hoodi-faucet.pk910.de/ . Hoodi ETH was also distributed to many people who previously interacted with the Holesky network. You might already have some Hoodi ETH in your wallet if you used Holesky so check first.

Adding a validator

Creating your validator keys and performing the deposit

There are 2 great tools to create your validator keys:

• GUI based: Wagyu Key Gen
• CLI based: ethstaker-deposit-cli

If you choose the Wagyu Key Gen application, make sure to select the Hoodi network and follow the instructions provided. If you are using the #cheap-hoodi-validator process, you will need to use 0x4D496CcC28058B1D74B7a19541663E21154f9c84 as your withdrawal address. This is only required for that process. When on Mainnet, you should use a withdrawal address you control if you want to use one.

If you choose the ethstaker-deposit-cli application, here is how to create your validator keys. Make sure to replace the 0x4D496CcC28058B1D74B7a19541663E21154f9c84 withdrawal address with your own address that you control if you need or want to:

$ cd ~
$ wget https://github.com/eth-educators/ethstaker-deposit-cli/releases/download/v1.1.0/ethstaker_deposit-cli-08f1e66-linux-amd64.tar.gz
$ tar xvf ethstaker_deposit-cli-08f1e66-linux-amd64.tar.gz
$ rm ethstaker_deposit-cli-08f1e66-linux-amd64.tar.gz
$ cd ethstaker_deposit-cli-08f1e66-linux-amd64/
$ ./deposit new-mnemonic --num_validators 1 --chain hoodi --execution_address 0x4D496CcC28058B1D74B7a19541663E21154f9c84
$ ls -d $PWD/validator_keys/*

Make sure to store your keystore password and your mnemonic somewhere safe. You should end up with a deposit file (starts with deposit_data- and ends with .json) and one or more keystore files (starts with keystore- and ends with .json), 1 per validator. Copy them around if needed. Make sure your deposit file and your keystore files are in a known and accessible location on your machine.

Next we will need to perform your deposit. If you used the #cheap-hoodi-validator process, you can perform your deposit on https://cheap.hoodi.launchpad.ethstaker.cc/ . If you managed to obtained 32 Hoodi ETH, you can use the official Hoodi launchpad on https://hoodi.launchpad.ethereum.org/ .

Configuring your Lodestar validator client

Create a dedicated user for running the Lodestar validator client, create a directory for holding the data and assign the proper permissions.

$ sudo useradd --no-create-home --shell /bin/false lodestarvalidator
$ sudo mkdir -p /var/lib/lodestar/validators
$ sudo chown -R lodestarvalidator:lodestarvalidator /var/lib/lodestar/validators
$ sudo chmod 700 /var/lib/lodestar/validators

Import your keystore that includes your validator key for the Lodestar validator client. Running the first command will prompt you for that keystore password. Make sure to enter it correctly and avoid leaving it blank. Make sure to replace /path/to/keystores with the actual path to your keystores created in the previous step.

$ sudo lodestar validator import \
    --importKeystores /path/to/keystores \
    --dataDir /var/lib/lodestar/validators \
    --network hoodi
$ sudo chown -R lodestarvalidator:lodestarvalidator /var/lib/lodestar/validators

Create a systemd service config file to configure the Lodestar validator client service.

$ sudo nano /etc/systemd/system/lodestarvalidator.service

Paste the following service configuration into the file. Exit and save once done (Ctrl + X, Y, Enter). Make sure to replace the 0x0000000000000000000000000000000000000000 address with your own Ethereum address that you control where you want to receive the transaction tips.

[Unit]
Description=Lodestar Validator Client (Hoodi)
Wants=network-online.target
After=network-online.target

[Service]
User=lodestarvalidator
Group=lodestarvalidator
Type=simple
Restart=always
RestartSec=5
ExecStart=lodestar validator \
    --network hoodi \
    --dataDir /var/lib/lodestar/validators \
    --graffiti EthStaker \
    --metrics true \
    --suggestedFeeRecipient 0x0000000000000000000000000000000000000000

[Install]
WantedBy=multi-user.target

Reload systemd to reflect the changes and start the service. Check status to make sure it’s running correctly.

$ sudo systemctl daemon-reload
$ sudo systemctl start lodestarvalidator.service
$ sudo systemctl status lodestarvalidator.service

It should say active (running) in green text. If not then go back and repeat the steps to fix the problem. Press Q to quit (will not affect the Lodestar validator client service).

Enable the Lodestar validator client service to automatically start on reboot.

$ sudo systemctl enable lodestarvalidator.service

You can watch the live messages from your Lodestar validator client logs using this command.

$ sudo journalctl -f -u lodestarvalidator.service -o cat | ccze -A

Press Ctrl + C to stop showing those messages.

Support

If you have any question or if you need additional support, make sure to get in touch with the EthStaker community on:

• Discord: dsc.gg/ethstaker
• Reddit: reddit.com/r/ethstaker

Credits

Based on Somer Esat's guide.