Lido advances EasyTrack management of its MEV relay allowlist

What happened

Lido's Snapshot supported adding EasyTrack factories through which the Relay Maintenance Committee could add, edit, or remove entries in the MEV-Boost Relay Allowed List.

What changed

The proposed design would make EasyTrack's EVMScriptExecutor the allowlist manager and use the Relay Maintenance Committee as trusted caller, replacing a manual multisignature update workflow with challengeable EasyTrack motions.

What did not change

The factories and manager-role change were not deployed in March. The Snapshot did not itself modify any relay entry or remove LDO-holder oversight.

Confirmed

• Lido node operators are required to use at least one relay from the mandatory category of the allowlist.
• The proposal specified Add, Edit, and Remove MEV-Boost relay factories and an EVMScriptExecutor manager role.
• The March Snapshot reached quorum and passed.
• Security audit and on-chain execution were identified as later prerequisites.

Still open

• Final factory code, deployed addresses, audit results, and on-chain authorization were pending during March.
• The operational effect on challenge periods and emergency-brake procedures required verification after deployment.
• No specific relay addition, removal, or reclassification was authorized by this event.

What it means for an advisor

• Review the Lido control map for the proposed manager, trusted-caller, challenge, and emergency-brake paths.
• Verify final contracts and on-chain authorization before treating the workflow as operative.
• Continue monitoring relay concentration and availability separately from the governance mechanism.