Teku VC
Download Teku
Follow the steps in this previous section to download Teku if you have not done so.
Teku BNCreate a new user account
Prepare the validator keystores
1) Create 3 new folders to store the validator client data, validator keystore, and the validator keystore password
2) Copy the validator keystores and it's password file into their respective folders
3) Change the owner of this folder to the teku user
4) Restrict permissions on this new folder such that only the owner is able to read, write, and execute files in this folder
Aside from the file extension, the validator_keystore_password file will need to be named identically as the validator signing keystore file (e.g. keystore-m-123.json, keystore-m-123.txt)
Configure the validator client service
Create a systemd configuration file for the Teku Validator Client service to run in the background.
Paste the configuration parameters below into the file:
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 Validator Client configuration summary:
--network
: Run the validator client service on the ETH Holesky testnet--data-path
: Specify the directory for Teku to store the validator info--validator-keys
: File path to the directory where your validator signing keystore and corresponding plain text password file are stored. Aside from the file extension (e.g. .json vs .txt), the password file will need to be named identically as the validator signing keystore file. For example:--beacon-node-api-endpoint
: URLs to connect to the main and backup consensus clients if any. This needs to be the same IP address set in your consensus client. Refer back here if you don't remember it.--validators-proposer-default-fee-recipient
: ETH wallet address to receive rewards from block proposals and MEV bribes--validators-proposer-blinded-blocks-enabled
: Required when using external builders to build blocks (e.g. MEV relays)--validators-graffiti
: Optional text to display on-chain when your validator proposes a block--metrics-enabled
: Enable metrics for monitoring--metrics-port
: Port to retrieve metrics for monitoring--doppelganger-detection-enabled
: Helps prevents slashing due to double signing by checking if your validator keys are already active on the network. Not a fool-proof solution.
Start the Teku Validator Client service
Reload the systemd daemon to register the changes made, start the Teku Validator Client, and check its status to make sure its running.
The output should say the Teku Validator Client is “active (running)”. Press CTRL-C to exit and the Teku Validator Client will continue to run.
Use the following command to check the logs for any warnings or errors:
Expected output:
Press CTRL-C
to exit.
If the Teku Validator Client service is running smoothly, we can now enable it to fire up automatically when rebooting the system.
Expected output:
Remove duplicates of validator keystores
To prevent configuration mistakes leading to double signing in the future, remove duplicate copies of the validator signing keystores once everything is running smoothly.
Resources
Documentation: https://docs.teku.consensys.io/introduction
Discord: https://discord.gg/consensys (Select the Teku channel)
Last updated