Introduce EasyTrack Factories for Managing MEV-Boost Relay Allowed List

Proposals
1

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!

16 Likes
2

The MEV-Boost Relay Allow List has the crucial function of guiding Node Operators to the relays that are expected to be used in their operations.
Its curation by the RMC is important, but at this point low maintenance job.
Having good people on the committee - trustworthy, high profile, doxxed people, helps with the trust and the mitigation of takeovers to favor parties or harm Lido. If we want these people to not be overburdened by bureaucracy and coordination, and therefore make them more likely to stick around, EasyTrack should be the way to go.

6 Likes
3

Hey! MixBytes team here :raised_hands:

Recently, 4 security researchers reviewed the specification for the changes made to the Easy Track EVM Factories. These changes introduce the management of the MEV Boost Relay Allowed List contract, enabling the creation of motions to add, remove, and edit relays in the Allow List through the EasyTrack contract.

The description of the EVMScript Factory calldata checks is sufficient and ensures compatibility, meaning it won’t cause any disruptions. Additionally, all the newly introduced function interfaces are correct.

We reviewed the pull request introducing AddMEVBoostRelays.sol, RemoveMEVBoostRelays.sol, and EditMEVBoostRelays.sol contracts to gain a deeper understanding of the changes. However, we did not conduct a full audit on these contracts; it was more of an architectural overview.

All operations previously performed by the RMC committee on the Relays Allow List will now be executed through Easy Track motions, maintaining full functionality without any limitations.

We also examined the proposal to extend the On-Chain Voting Duration, which could theoretically allow Easy Track to front-run an ongoing DAO vote, as the Lido Agent Multisig is kept as the owner of the MEVBoostRelayAllowedList.vy contract. However, since Easy Track motions can only be initiated by trusted callers and there is an Emergency Brakes Multisig capable of pausing Easy Track, this does not pose any security risks.

7 Likes
4

Snapshot vote started

The MEV-Boost Relay Allowed List management via Easy Track Snapshot has started! Please cast your votes before Mon, 24 Mar 2025 16:00:00 GMT :folded_hands:

1 Like
5

Snapshot vote ended

The MEV-Boost Relay Allowed List management via Easy Track Snapshot has reached a quorum and completed!
The results are:
For: 62.8M LDO
Against: 16.597 LDO

2 Likes
6

Hey-hey! We’re thrilled to share that our Easy Track factories for MEV-Boost Relay Allowed List management have now been successfully deployed on both Mainnet and Hoodi testnet! You can explore the contracts at the links below:

Mainnet

Hoodi (Testnet)

Also, our external audit was wrapped up with zero findings! The full audit report includes deployed contract addresses and is available here:

Smart contract code currently can be found in the easy-track GitHub repo.

1 Like
7

:chequered_flag: Vote #187 is now live — make sure to review and vote!

This vote contains separate updates approved by Lido DAO via Snapshot voting, including the addition of Easy Track factories to manage the MEV-Boost Relay Allowed List (items 10-13).

:date: Deadline

The vote is open until the end of the main phase: May 24, 14:17 UTC.

:mag_right: Want to verify vote items?

Follow this guide to check the execution steps and calldata.

8

:high_voltage: Vote #187 did not reach quorum and will be rescheduled for May 27.

Please stay tuned for the new vote and make sure to participate once it goes live.

9

I propose to once again raise the issue of increasing the voting period by at least another 2 days

The previous 1-day increase for YES votes was too small

10

:rocket: Vote #188 has just started!

This is a rerun of Vote #187, featuring the same set of proposals.

:alarm_clock: Voting is open until the end of the main phase: May 30, 09:00 UTC.

Follow this guide for instructions on reviewing and verifying vote items.

Your voice matters! :two_hearts:

11

Vote #188: Passed and Enacted! :rocket:

Thanks to everyone who took part in the voting process.

Results:

:check_mark: Yes - 51315931.2 (5.13%)
:cross_mark: No - 5.1 (0.01%)

We’re grateful for your trust and continued support! :pink_heart:

3 Likes