Verifying Fee Recipient Registered on MEV Relays

Checker Script

Mainnet

Install dependencies and activate a Python virtual environment.

sudo apt update
sudo apt install git python3-venv python3-full python3-requests
# Activate Python virtual environment
python3 -m venv ~/check_relay_env
source ~/check_relay_env/bin/activate
pip install web3 requests

Download the Fee Recipient checker script (Source).

git clone https://gist.github.com/bc188884f6bdc1ce2c65a949e84b0dc5.git check_no_relays
cd check_no_relays

Set the RPC endpoint using your local execution client or one of the free publicly available ones here: https://ethereumnodes.com/

export RPC_URL="http://127.0.0.1:8545"

or;

export RPC_URL="https://eth.llamarpc.com"

Run the Checker Script and enter your CSM Node Operator ID when prompted.

python3 check_no_relays.py

Expected output:

Example output using dummy pubkeys

Once done, you can deactivate the Python virtual environment.

deactivate

Troubleshooting:

ConnectionRefusedError: [Errno 111] Connection refused

If you face a "connection refused" error as seen above, it either means the RPC endpoint of your Execution Client is not enabled or the RPC_URL used is incorrect

How to fix?

Eth Docker

Edit the .env file.

nano ~/eth-docker/.env

Add :el-shared.yml to the back of the COMPOSE_FILE= line.

Save and exit with CTRL+O, ENTER, CTRL+X.

Restart the Eth Docker stack with ethd down then ethd up.

systemd

Enable RPC or HTTP endpoint on your Execution Client.

sudo nano /etc/systemd/system/EXECUTION_CLIENT.service
# replace EXECUTION_CLIENT with the actual file name

Make sure the following flags are added.

1. Geth, Reth, Erigon: --http

2. Nethermind: --JsonRpc.Enabled

3. Besu: --rpc-http-enabled

Save and exit with CTRL+O, ENTER, CTRL+X.

Restart your execution client.

sudo systemctl daemon-reload
sudo systemctl restart EXECUTION_CLIENT
# replace EXECUTION_CLIENT with the actual file name

Eth Pillar

Enabled by default.

Manual Check

For each MEV Relay you have configured, replace <VALIDATOR_PUBKEY> for each of the commands below and run them on your terminal.

Then verify that the Fee Recipient Address matches with the Lido Execution Layer Rewards Vaults on Mainnet or Holesky depending on your setup (Source).

Example output:

{"message":{"fee_recipient":"0x388C818CA8B9251b393131C08a736A67ccB19297","gas_limit":"30000000","timestamp":"1739938746","pubkey":"0x...."},"signature":"0x...."}

Mainnet

Lido Execution Layer Rewards Vault on mainnet = 0x388C818CA8B9251b393131C08a736A67ccB19297

1) Titan Relay Global (Mainnet) (Non-filtering):

curl https://0x8c4ed5e24fe5c6ae21018437bde14769[e-mail]/relay/v1/data/validator_registration?pubkey=<VALIDATOR_PUBKEY>

2) Titan Relay Regional (Mainnet) (Filtering):

curl https://0x8c4ed5e24fe5c6ae21018437bde14769[e-mail]/relay/v1/data/validator_registration?pubkey=<VALIDATOR_PUBKEY>

3) Agnostic Relay (Mainnet)

curl https://0xa7ab7a996c8584251c8f925da3170bdf[e-mail]/relay/v1/data/validator_registration?pubkey=<VALIDATOR_PUBKEY>

4) Ultrasound Relay

curl https://0xa1559ace749633b997cb3fdacffb890a[e-mail]/relay/v1/data/validator_registration?pubkey=<VALIDATOR_PUBKEY>

5) Aestus Relay (Mainnet)

curl https://0xa15b52576bcbf1072f4a011c0f99f9fb[e-mail]/relay/v1/data/validator_registration?pubkey=<VALIDATOR_PUBKEY>

6) Manifold SecureRPC (Mainnet)

curl https://0x98650451ba02064f7b000f5768cf0cf4[e-mail]/relay/v1/data/validator_registration?pubkey=<VALIDATOR_PUBKEY>

7) Flashbots (Mainnet)

curl https://0xac6e77dfe25ecd6110b8e780608cce0d[e-mail]/relay/v1/data/validator_registration?pubkey=<VALIDATOR_PUBKEY>

8) bloXroute Max-Profit (Mainnet)

curl https://0x8b5d2e73e2a3a55c6c87b8b6eb92e014[e-mail]/relay/v1/data/validator_registration?pubkey=<VALIDATOR_PUBKEY>

9) bloXroute Regulated (Mainnet)

curl https://0xb0b07cd0abef743db4260b0ed50619cf[e-mail]/relay/v1/data/validator_registration?pubkey=<VALIDATOR_PUBKEY>

Testnet (WIP)

Lido Execution Layer Rewards Vault on Holesky = 0xE73a3602b99f1f913e72F8bdcBC235e206794Ac8