Method 1: Configure on validator keys

Validator Clients

Teku

Assuming your Teku validator client is already set up, stop your Teku validator client.

sudo systemctl stop tekuvalidator.service

Find 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_FILEPATH

You 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.json

Paste 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"

• Holesky

suggested_fee_recipient: "0xE73a3602b99f1f913e72F8bdcBC235e206794Ac8"

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/validator

Adding 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.service

Add 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 (Holesky)
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=holesky \
  --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-proposer-blinded-blocks-enabled=true \
  --validators-graffiti="<your_graffiti_of_choice>" \
  --metrics-enabled=true \
  --metrics-port=8108 \
  --doppelganger-detection-enabled=true 

[Install]
WantedBy=multi-user.target

CTRL+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.service

Monitor for errors.

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

Nimbus

Configure a separate validator client and set the fee_recipient address to the Lido Execution Layer Rewards Vault there. Refer to the subpage below.

Method 2: Configure on separate validator client

Lodestar

The --proposerSettingsFile feature of Lodestar and its format is in alpha and subject to change. Hence we will fallback to running a separate validator client to customise the fee_recipient address.

Configure a separate validator client and set the fee_recipient address to the Lido Execution Layer Rewards Vault there. Refer to the following subpage.

Method 2: Configure on separate validator client

Lighthouse

Assuming you have set up your Lighthouse validator client and imported your CSM validator keystores. Stop your validator client.

sudo systemctl stop lighthousevalidator.service

Then, 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 configurations

Find 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_FILEPATH

and add the following line under each keystore as a new line. Note: Take note of the exact indentation.

• Mainnet

suggested_fee_recipient: "0x388C818CA8B9251b393131C08a736A67ccB19297"

• Holesky

suggested_fee_recipient: "0xE73a3602b99f1f913e72F8bdcBC235e206794Ac8"

Example with Mainnet fee recipient:

---
- enabled: true
  voting_public_key: 0xa1a6d4a72db3fff3a81401cb9a80e1a7d18a96c3a6c3c9b50531e3b02e50b2baeba06e3a7c9fe24374e48091006b11f7
  description: ''
  type: local_keystore
  voting_keystore_path: /var/lib/lighthouse_validator/validators/0xa1a6d4a72db3fff3a81401cb9a80e1a7d18a96c3a6c3c9b50531e3b02e50b2baeba06e3a7c9fe24374e48091006b11f7/keystore-m>
  voting_keystore_password: password
  suggested_fee_recipient: "0x388C818CA8B9251b393131C08a736A67ccB19297"
- enabled: true
  voting_public_key: 0x8e2a8abfeeca058d757f6d6ff5c058c61ab1d40804c28298d44bfe4486265c96e5d30f781a2a3cee6e2b250a85c40e38
  description: ''
  type: local_keystore
  voting_keystore_path: /var/lib/lighthouse_validator/validators/0x8e2a8abfeeca058d757f6d6ff5c058c61ab1d40804c28298d44bfe4486265c96e5d30f781a2a3cee6e2b250a85c40e38/keystore-m>
  voting_keystore_password: password
  suggested_fee_recipient: "0x388C818CA8B9251b393131C08a736A67ccB19297"

Restart your Lighthouse validator client.

sudo systemctl start lighthousevalidator.service
sudo systemctl status lighthousevalidator.service

Monitor for errors.

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

Prysm

Assuming your Prysm validator client is already set up, stop your Prysm validator client.

sudo systemctl stop prysmvalidator.service

Find 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_FILEPATH

You 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.json

Paste 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"

• Holesky

suggested_fee_recipient: "0xE73a3602b99f1f913e72F8bdcBC235e206794Ac8"

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/validator

Adding 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.service

Add 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 (Holesky)
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 \
  --holesky \
  --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.target

CTRL+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.service

Monitor for errors.

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

Automation Tools

ETH Docker

With ETH Docker running (i.e., ethd up), run

./ethd keys list

then

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

ETH Pillar

Not straightforward. Designed to assign custom fee_recipient addresses by running a separate validator client. Refer to the subpage below, under "Automation Tools"

Method 2: Configure on separate validator client