Method 1: Configure on validator keys
Validator Clients
Assuming your Teku validator client is already set up, stop your Teku validator client.
sudo systemctl stop tekuvalidator.serviceFind the pubkey values of your own non-CSM validator keystores generated.
sudo find /var/lib -name "keystore*.json"For each resulting filepath, run:
grep -oP '"pubkey": *"\K[^"]+' RESULTING_FILEPATHYou should now have a list of all your own non-CSM validator keystore pubkeys.
Create a custom proposer configuration file.
sudo nano /var/lib/teku_validator/validator/proposer_configuration.jsonPaste the following contents into the file.
{
"proposer_config": {
"YOUR_OWN_VALIDATOR_PUBKEY_(NOT_CSM)_01": {
"fee_recipient": "YOUR_OWN_FEE_RECIPIENT_ADDRESS",
"builder": {
"enabled": true
}
},
"YOUR_OWN_VALIDATOR_PUBKEY_(NOT_CSM)_02": {
"fee_recipient": "YOUR_OWN_FEE_RECIPIENT_ADDRESS",
"builder": {
"enabled": true
}
},
"YOUR_OWN_VALIDATOR_PUBKEY_(NOT_CSM)_03": {
"fee_recipient": "YOUR_OWN_FEE_RECIPIENT_ADDRESS",
"builder": {
"enabled": true
}
}
},
"default_config": {
"fee_recipient": "LIDO_EXECUTION_LAYER_REWARDS_VAULT",
"builder": {
"enabled": true
}
}
}Replace YOUR_OWN_VALIDATOR_PUBKEY_(NOT_CSM) with your own actual validator pubkeys (NOT CSM).
Replace YOUR_OWN_FEE_RECIPIENT_ADDRESS with your desired wallet address.
Replace LIDO_EXECUTION_LAYER_REWARDS_VAULT with the following options.
Mainnet
suggested_fee_recipient: "0x388C818CA8B9251b393131C08a736A67ccB19297"Hoodi
suggested_fee_recipient: "0x9b108015fe433F173696Af3Aa0CF7CDb3E104258"CTRL+O, ENTER, CTRL+X to save and exit.
Set the permissions of the custom proposer configuration file.
sudo chown -R teku_validator:teku_validator /var/lib/teku_validator/validatorAdding more non-CSM validator keystores:
If you want to add more of your own validator keystores, replicate the following segment, taking note of the indentation.
"YOUR_OWN_VALIDATOR_PUBKEY_(NOT_CSM)_03": {
"fee_recipient": "YOUR_OWN_FEE_RECIPIENT_ADDRESS",
"builder": {
"enabled": true
}
}CTRL+O, ENTER, CTRL+X to save and exit.
Edit the Teku validator client service file.
sudo nano /etc/systemd/system/tekuvalidator.serviceAdd the --validators-proposer-config flag and point it to the proposer_configuration.json file. Then remove the --validators-proposer-default-fee-recipient flag. e.g.,
[Unit]
Description=Teku Validator Client
Wants=network-online.target
After=network-online.target
[Service]
User=teku_validator
Group=teku_validator
Type=simple
Restart=always
RestartSec=5
Environment="JAVA_OPTS=-Xmx6g"
Environment="TEKU_OPTS=-XX:-HeapDumpOnOutOfMemoryError"
ExecStart=/usr/local/bin/teku/bin/teku vc \
--network=hoodi \
--data-path=/var/lib/teku_validator \
--validator-keys=/var/lib/teku_validator/validator_keystores:/var/lib/teku_validator/keystore_password \
--beacon-node-api-endpoint=http://<Internal_IP_address>:5051 \
--validators-proposer-config=/var/lib/teku_validator/validator/proposer_configuration.json \
--validators-builder-registration-default-enabled=true \
--validators-graffiti="<your_graffiti_of_choice>" \
--metrics-enabled=true \
--metrics-port=8108 \
--doppelganger-detection-enabled=true
[Install]
WantedBy=multi-user.targetCTRL+O, ENTER, CTRL+X to save and exit.
Restart your Teku validator client.
sudo systemctl daemon-reload
sudo systemctl start tekuvalidator.service
sudo systemctl status tekuvalidator.serviceMonitor for errors.
sudo journalctl -fu tekuvalidator -o cat | ccze -AConfigure a separate validator client and set the fee_recipient address to the Lido Execution Layer Rewards Vault there. Refer to the subpage below.
Create a custom proposer_settings.yml file.
sudo nano /var/lib/lodestar_validator/proposer_settings.ymlUse the following template and make the necessary edits.
proposer_config:
'YOUR_OWN_VALIDATOR_PUBKEY_(NOT_CSM)_01':
graffiti: 'non-CSM graffiti'
strict_fee_recipient_check: true
fee_recipient: 'YOUR_OWN_FEE_RECIPIENT_ADDRESS'
builder:
enabled: true
gas_limit: "30000000"
'YOUR_OWN_VALIDATOR_PUBKEY_(NOT_CSM)_02':
fee_recipient: 'YOUR_OWN_FEE_RECIPIENT_ADDRESS'
builder:
enabled: "true"
gas_limit: "30000000"
default_config:
graffiti: 'CSM graffiti'
strict_fee_recipient_check: true
fee_recipient: 'LIDO_EXECUTION_LAYER_REWARDS_VAULT'
builder:
enabled: true
gas_limit: "30000000"
selection: "maxprofit"
boost_factor: "100"Replace YOUR_OWN_VALIDATOR_PUBKEY_(NOT_CSM) with your own actual validator pubkeys (NOT CSM).
Replace YOUR_OWN_FEE_RECIPIENT_ADDRESS with your desired wallet address.
Replace LIDO_EXECUTION_LAYER_REWARDS_VAULT with the following options.
Mainnet
suggested_fee_recipient: "0x388C818CA8B9251b393131C08a736A67ccB19297"Hoodi
suggested_fee_recipient: "0x9b108015fe433F173696Af3Aa0CF7CDb3E104258"CTRL+O, ENTER, CTRL+X to save and exit.
Set the permissions of the custom proposer configuration file.
sudo chown -R lodestar_validator:lodestar_validator /var/lib/lodestar_validatorAdding more non-CSM validator keystores:
If you want to add more of your own validator keystores, replicate the following segment and place them under the proposer_config section, taking note of the indentation.
proposer_config:
'YOUR_OWN_VALIDATOR_PUBKEY_(NOT_CSM)':
fee_recipient: 'YOUR_OWN_FEE_RECIPIENT_ADDRESS'
builder:
enabled: "true"
gas_limit: "30000000"CTRL+O, ENTER, CTRL+X to save and exit.
Edit the docker-compose.yml file in the Lodestar folder.
cd ~/lodestar_validator
sudo nano docker-compose.ymlAdd the --proposerSettingsFile flag and point it to the proposer_settings.yml file.
- --proposerSettingsFile
- /var/lib/lodestar_validator/proposer_settings.ymlThen remove the following flags.
- --suggestedFeeRecipient
- "<your_designated_ETH_wallet_address>"New example:
services:
validator_client:
image: chainsafe/lodestar:latest
container_name: lodestar_validator
user: <UID>:<GID>
restart: unless-stopped
volumes:
- /var/lib/lodestar_validator:/var/lib/lodestar_validator
command:
- validator
- --dataDir
- /var/lib/lodestar_validator
- --importKeystores
- /var/lib/lodestar_validator/validator_keystores
- --importKeystoresPassword
- /var/lib/lodestar_validator/keystore_password/<validator_signing_keystore_password_file_name>.txt
- --network
- hoodi
- --beaconNodes
- http://127.0.0.1:5052
- --builder
- --proposerSettingsFile
- /var/lib/lodestar_validator/proposer_settings.yml
- --doppelgangerProtection
- --metrics
- --metrics.port
- "5064"
- --graffiti
- "your_graffiti_of_choice"
environment:
NODE_OPTIONS: --max-old-space-size=2048
ports:
- "5064:5064"CTRL+O, ENTER, CTRL+X to save and exit.
Restart your Lodestar validator client.
docker compose down
docker compose up -dMonitor for errors.
docker logs lodestar_validator -fMethod 2:
Alternatively, to configure a separate validator client and set the fee_recipient address to the Lido Execution Layer Rewards Vault there, refer to the following subpage.
Assuming you have set up your Lighthouse validator client and imported your CSM validator keystores. Stop your validator client.
sudo systemctl stop lighthousevalidator.serviceThen, edit the validator_definitions.yml file with the designated fee_recipeint address.
sudo nano /var/lib/lighthouse_validator/validators/validator_definitions.yml
# Actual filepath might vary according to your configurationsFind the pubkeys of each of your CSM validator keystores.
sudo find /var/lib -name "keystore*.json"For each resulting filepath, run:
grep -oP '"pubkey": *"\K[^"]+' RESULTING_FILEPATHand add the following line under each keystore as a new line. Note: Take note of the exact indentation.
Mainnet
suggested_fee_recipient: "0x388C818CA8B9251b393131C08a736A67ccB19297"Hoodi
suggested_fee_recipient: "0x9b108015fe433F173696Af3Aa0CF7CDb3E104258"Example with Mainnet fee recipient:
To be appended, not replacing your existing file contents
- enabled: true
voting_public_key: CSM_VALIDATOR_PUBKEY_01
description: ''
type: local_keystore
voting_keystore_path: /var/lib/lighthouse_validator/validators/0xa1a6d4a72db3fff3a81401cb9a80e1a7d18a96c3a6c3c9b50531e3b02e50b2baeba06e3a7c9fe24374e48091006b11f7/keystore-m>
voting_keystore_password: password
suggested_fee_recipient: "0x388C818CA8B9251b393131C08a736A67ccB19297"
builder_boost_factor: 100
- enabled: true
voting_public_key: CSM_VALIDATOR_PUBKEY_02
description: ''
type: local_keystore
voting_keystore_path: /var/lib/lighthouse_validator/validators/0x8e2a8abfeeca058d757f6d6ff5c058c61ab1d40804c28298d44bfe4486265c96e5d30f781a2a3cee6e2b250a85c40e38/keystore-m>
voting_keystore_password: password
suggested_fee_recipient: "0x388C818CA8B9251b393131C08a736A67ccB19297"
builder_boost_factor: 100Restart your Lighthouse validator client.
sudo systemctl start lighthousevalidator.service
sudo systemctl status lighthousevalidator.serviceMonitor for errors.
sudo journalctl -fu lighthousevalidator -o cat | ccze -AAssuming your Prysm validator client is already set up, stop your Prysm validator client.
sudo systemctl stop prysmvalidator.serviceFind the pubkey values of your own non-CSM validator keystores generated.
sudo find /var/lib -name "keystore*.json"For each resulting filepath, run:
grep -oP '"pubkey": *"\K[^"]+' RESULTING_FILEPATHYou should now have a list of all your own non-CSM validator keystore pubkeys.
Create a custom proposer configuration file.
sudo nano /var/lib/prysm_validator/validator/proposer_configuration.jsonPaste the following contents into the file.
{
"proposer_config": {
"YOUR_OWN_VALIDATOR_PUBKEY_(NOT_CSM)_01": {
"fee_recipient": "YOUR_OWN_FEE_RECIPIENT_ADDRESS",
"builder": {
"enabled": true
}
},
"YOUR_OWN_VALIDATOR_PUBKEY_(NOT_CSM)_02": {
"fee_recipient": "YOUR_OWN_FEE_RECIPIENT_ADDRESS",
"builder": {
"enabled": true
}
},
"YOUR_OWN_VALIDATOR_PUBKEY_(NOT_CSM)_03": {
"fee_recipient": "YOUR_OWN_FEE_RECIPIENT_ADDRESS",
"builder": {
"enabled": true
}
}
},
"default_config": {
"fee_recipient": "LIDO_EXECUTION_LAYER_REWARDS_VAULT",
"builder": {
"enabled": true
}
}
}Replace YOUR_OWN_VALIDATOR_PUBKEY_(NOT_CSM) with your own actual validator pubkeys (NOT CSM).
Replace YOUR_OWN_FEE_RECIPIENT_ADDRESS with your desired wallet address.
Replace LIDO_EXECUTION_LAYER_REWARDS_VAULT with the following options.
Mainnet
suggested_fee_recipient: "0x388C818CA8B9251b393131C08a736A67ccB19297"Hoodi
suggested_fee_recipient: "0x9b108015fe433F173696Af3Aa0CF7CDb3E104258"CTRL+O, ENTER, CTRL+X to save and exit.
Set the permissions of the custom proposer configuration file.
sudo chown -R prysm_validator:prysm_validator /var/lib/prysm_validator/validatorAdding more non-CSM validator keystores:
If you want to add more of your own validator keystores, replicate the following segment, taking note of the indentation.
"YOUR_OWN_VALIDATOR_PUBKEY_(NOT_CSM)_03": {
"fee_recipient": "YOUR_OWN_FEE_RECIPIENT_ADDRESS",
"builder": {
"enabled": true
}
}CTRL+O, ENTER, CTRL+X to save and exit.
Edit the Prysm validator client service file.
sudo nano /etc/systemd/system/prysmvalidator.serviceAdd the --proposer-settings-file flag and point it to the proposer_configuration.json file. Then remove the --suggested-fee-recipient flag. e.g.,
[Unit]
Description=Prysm Validator Client
Wants=network-online.target
After=network-online.target
[Service]
User=prysmvalidator
Group=prysmvalidator
Type=simple
Restart=always
RestartSec=5
ExecStart=/usr/local/bin/prysmvalidator \
--accept-terms-of-use \
--<hoodi_or_mainnet> \
--datadir=/var/lib/prysm_validator \
--enable-builder \
--beacon-rpc-provider=<Internal_IP_address>:4000 \
--beacon-rpc-gateway-provider=<Internal_IP_address>:5051 \
--wallet-dir=/var/lib/prysm_validator \
--wallet-password-file=/var/lib/prysm_validator/password.txt \
--monitoring-port=8108 \
--proposer-settings-file=/var/lib/prysm_validator/validator/proposer_configuration.json \
--graffiti="<your_graffiti>" \
--enable-doppelganger
[Install]
WantedBy=multi-user.targetCTRL+O, ENTER, CTRL+X to save and exit.
Restart your Prysm validator client.
sudo systemctl daemon-reload
sudo systemctl start prysmvalidator.service
sudo systemctl status prysmvalidator.serviceMonitor for errors.
sudo journalctl -fu prysmvalidator -o cat | ccze -AAutomation Tools
With ETH Docker running (i.e., ethd up), run
./ethd keys listthen
./ethd keys set-recipient 0xPUBKEY 0xADDRESS with the public key of the key you wish to set a separate fee recipient for, and the Ethereum address fees should go to.
Not straightforward. Designed to assign custom fee_recipient addresses by running a separate validator client. Refer to the subpage below, under "Automation Tools"
Last updated