tl;dr
The Lido DAO Infra workstream proposes deploying three new EasyTrack EVM script factories with the Relay Maintenance Committee (RMC) as a trusted caller to manage the MevBoostRelayAllowedList contract.
Motivation
The current process of managing the MEV-Boost Relay Allowed List involves several steps, including posting a change proposal on the Research Forum, awaiting the challenge period, and coordinating with RMC participants to create, verify, and sign the change transaction.
Switching to EasyTrack automation will reduce manual workload, minimize delays, and simplify management of the List. This improves efficiency for the RMC while keeping governance oversight intact and even strengthening accountability via EasyTrack for LDO holders.
Context
The MEV Boost Relay Allowed List plays an important role.
All node operators across Lido’s staking modules are required to use at least one of the list’s entries labeled as “must use some” and as many as they want from those labeled as “may use” in their consensus layer client (or out-of-protocol proposer-builder separation validator sidecar) configuration. This helps with Ethereum’s decentralization while also enabling MEV extraction for the Lido protocol.
The Relay Maintenance Committee (RMC), which vets relays and manages the list on behalf of the community, occasionally needs to update its entries. Changes may be necessary due to a relay service being discontinued, the need for removal for other reasons, a community-driven reclassification between the “must use some” and “may use” categories, or the approval of a newly vetted relay seeking to provide services to Lido.
Details
To make the process simple and reliable, we propose implementing and adding three new EVM script factories to EasyTrack:
- AddMEVBoostRelays
- EditMEVBoostRelays
- RemoveMEVBoostRelays
The names of these factories are self-explanatory: each will allow the commiteee to create EasyTrack motions to add, edit, or remove multiple entries from the MEV Boost Relay Allowed List.
In addition to enabling the new factories in EasyTrack, we’ll also need to set EasyTrack’s EVMScriptExecutor as the manager for the MEVBoostRelayAllowedList.
All references, including technical spec, contracts’ code and audit reports will be posted in this thread as soon as they become available.
Next Steps
If no objections are raised by the community, we will proceed by starting a Snapshot vote and then, after passing security audits, conduct an on-chain vote to enable the new factories in Q2 2025.
Stay tuned!
