Execution Layer Rewards Configuration
Node Operators who run validators for Lido are required to set the fee recipient for the relevant validators to the protocol-managed LidoExecutionLayerRewardsVault which manages Execution Layer Rewards. This address differs depending on the network (Mainnet, testnet, etc.) and is not the same as the Withdrawal Credentials address.
This smart contract address can also be retrieved by querying the elRewardsVault() method in the LidoLocator contract.
The address is also available in the Deployed Contracts docs page, labeled as Execution Layer Rewards Vault.
Fee recipient options for various Beacon Chain clients
Beacon chain clients offer a variety of methods for configuring the fee recipient. For some clients the fee recipient option should be applied with other options, see reference pages for specific client. Please note that most clients also support setting the fee recipient on a per-validator key basis (e.g. for Teku this can be achieved via the proposer config. Consult the docs for each client for specific instructions.
| Consensus client | CLI option | CLI reference page |
|---|---|---|
| Teku | --validators-proposer-default-fee-recipient=<ADDRESS> | Teku CLI options |
| Lighthouse | --suggested-fee-recipient=<ADDRESS> | Lighthouse Fee Recipient Config |
| Nimbus | --suggested-fee-recipient=<ADDRESS> | Nimbus Fee Recipient Info |
| Prysm | --suggested-fee-recipient=<ADDRESS> | Prysm CLI options |
| Lodestar | --chain.defaultFeeRecipient=<ADDRESS> | Lodestar CLI options |
MEV-Boost related options for various Beacon Chain clients
| Consensus client | CLI option | CLI reference page |
|---|---|---|
| Teku | --builder-endpoint=<URL> | Teku MEV integration |
| Lighthouse | BN: --builder=<URL> VC: --builder-proposals | Lighthouse MEV integration |
| Nimbus | --payload-builder=true --payload-builder-url=<URL> | Nimbus MEV integration |
| Prysm | --http-mev-relay=<URL> | Prysm MEV integration |
| Lodestar | BN: --builder --builder.urls=<URL> VC: --builder | Lodestar MEV integration |
Relays and MEV-Boost options
List of possible relays that have been approved by DAO can be fetched by querying the get_relays() method in MevBoostRelayAllowedList contract.
Mainnet
./mev-boost -mainnet -relay-check -relay <comma-separated relay urls>
Holešky
./mev-boost -holesky -relay-check -relay <comma-separated relay urls>
Full list of MEV-boost CLI options can be found here MEV-Boost CLI Options