DVT Home Staking Curriculum

Teku BN

Install the dependencies - Java Runtime Environment

sudo apt-get update
sudo add-apt-repository ppa:openjdk-r/ppa
sudo apt-get -y install openjdk-21-jre libjemalloc-dev

Download Teku

Download the latest version of Teku and run the checksum verification process to ensure that the downloaded file has not been tampered with.

cd
curl -LO https://artifacts.consensys.net/public/teku/raw/names/teku.tar.gz/versions/24.10.2/teku-24.10.2.tar.gz
echo "1cc76913f3b85987e2a60c9b94c6918d31773ebd3237c5fdf33de366fa259202 teku-24.10.2.tar.gz" | sha256sum --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.

teku-24.10.2.tar.gz: OK

If checksum is verified, extract the files and move them into the (/usr/local/bin) directory for neatness and best practice. Then, clean up the duplicated copies.

tar xvf teku-24.10.2.tar.gz
sudo cp -a teku-24.10.2 /usr/local/bin/teku
rm -r teku*

Configure the Teku Consensus Client

We will be running the consensus client and validator client of Teku 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 (teku) without server access for the Teku Consensus Client & 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 Teku Consensus Client & 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 teku

Create a directory for Teku 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 teku so that this user can read and write to the directory.

sudo mkdir -p /var/lib/teku_beacon
sudo chown -R teku:teku /var/lib/teku_beacon
sudo chmod 700 /var/lib/teku_beacon

If there are no errors, create a systemd configuration file for the Teku Consensus Client service to run in the background.

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

Paste the configuration parameters below into the file:

[Unit]
Description=Teku Beacon Node (Holesky)
Wants=network-online.target
After=network-online.target
[Service]
User=teku
Group=teku
Type=simple
Restart=always
RestartSec=5
Environment="JAVA_OPTS=-Xmx6g"
Environment="TEKU_OPTS=-XX:-HeapDumpOnOutOfMemoryError"
ExecStart=/usr/local/bin/teku/bin/teku \
  --network=holesky \
  --data-path=/var/lib/teku_beacon \
  --ee-endpoint=http://127.0.0.1:8551 \
  --ee-jwt-secret-file=/var/lib/jwtsecret/jwt.hex \
  --initial-state=https://holesky.beaconstate.ethstaker.cc/ \
  --metrics-enabled=true \
  --metrics-port=8009 \
  --p2p-port=9000 \
  --rest-api-enabled=true \
  --rest-api-interface=0.0.0.0 \
  --rest-api-host-allowlist=<Internal_IP_address> \
  --rest-api-port=5052 \
  --builder-endpoint=http://127.0.0.1:18550 \
  --validators-builder-registration-default-enabled=true \
  --builder-bid-compare-factor=100 \
  --p2p-nat-method=UPNP 

[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.

Teku Consensus Client configuration summary:

  1. --network: Run the Consensus Client service on the ETH Holesky testnet

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

  3. --ee-endpoint: URL to connect to the execution layer client

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

  5. --initial-state: Enables nearly instant syncing of the Consensus Client by pointing to one of the checkpoint sync URLs here - https://eth-clients.github.io/checkpoint-sync-endpoints/

  6. --metrics-enabled: Enable monitoring of Consensus Client metrics

  7. --p2p-port: Sets the port for peer-to-peer communication. Defaults to 9000.

  8. --rest-api-enabled: Allows the validator client to connect to this consensus client. Also allows monitoring endpoints to pull metrics from this service

  9. --rest-api-interface: Sets the IP address to connect to the REST API of the consensus client that will be used by the DVT clients. Use 0.0.0.0 here and restrict to specific host IP addresses of your device using --rest-api-host-allowlist.

  10. --rest-api-host-allowlist: Sets the IP address that is allowed 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

  11. --rest-api-port: Sets the port to connect to the consensus client

  12. --builder-endpoint: URL to connect to external builders (e.g. MEV relays)

  13. --validators-builder-registration-default-enabled: Required when using external builders to build blocks (e.g. MEV relays)

  14. --builder-bid-compare-factor: What is the multiplier (in %) of the value of externally-built blocks in order to outsource block building vs building blocks locally. Set to 100 to be indifferent. Default =90

  15. --p2p-nat-method=UPNP: Enables your Consensus Client to better discover and connect to other Consensus Clients in the ETH network without needing to use port forwarding

Start the Teku Consensus Client

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

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

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

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

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

Expected output:

Press Ctrl+C to exit monitoring.

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

sudo systemctl enable tekubeacon.service

Verify the Initial State roots (Checkpoint Sync)

  1. Go to https://holesky.beaconcha.in/ on your browser and search for the slot number (slot).

  2. Verify the Block Root and State Root with your journalctl output

  3. journalctl output

Resources

PreviousSet up and configure consensus layer clientNextNimbus BN

Last updated