The Ledger
Lido proposes trustless and trusted MEV tracks
Lido’s proposal keeps a permissionless route open to builders meeting Ethereum’s protocol requirements while requiring approval for bids with payments outside protocol guarantees. It sets out validator requirements, monitoring checks and conditions for existing entries on Lido’s Allowed List as Ethereum moves toward ePBS.

Lido’s 2026-11-04 proposal keeps one route open to any builder meeting Ethereum’s protocol requirements, while requiring Lido approval for builders or intermediaries whose bids include payments outside protocol guarantees. The proposed split adapts Lido’s MEV policy to Ethereum’s upcoming enshrined Proposer-Builder Separation (ePBS). The policy would remain mandatory for all Lido Node Operators.
ePBS supports trustless and trusted payments
Under ePBS, a bid can include two types of payment: a trustless value, owed once a proposer includes the bid whether or not the builder reveals the payload, and a trusted execution_payment, settled outside the protocol. The transport determines which payment types a bid can contain: bids sent over the p2p bidpool must have execution_payment set to zero, while bids sent over a direct Builder API connection can combine trustless and trusted payments. Every bid is attributable: bids are signed by a registered builder index, and self-built blocks are easily identifiable.
Validators broadcast signed preferences for upcoming slots that specify a fee recipient and gas limit. If a validator broadcasts no preference for a slot, it accepts no trustless bids for that slot; the trustless payment goes to the fee recipient named in the bid. Lido’s proposal requires every Lido validator to broadcast signed preferences naming the Lido EL Rewards Vault as fee recipient, and any bid accepted by a Lido validator must also name that vault.
Lido validators must maintain access to the permissionless builder market
All Lido validators must maintain access to the permissionless builder market introduced by ePBS, and p2p bid reception must remain enabled on every node capable of proposing a Lido block. Operators may also use direct connections or compatible middleware to access that market, provided those entries are limited to trustless bids, with max_execution_payment set to zero. Node Operators are responsible for builder registrations.
Builders and intermediaries offering payments outside Ethereum’s protocol guarantees must be approved through Lido’s Allowed List. Node Operators must configure at least one, but as many as possible, entry from the designated “must use some” list, and may configure any number of entries from the general Allowed List. Relays running an open auction remain the preferred entry type; direct builder connections may also be approved, subject to appropriate assessment of reliability, transparency and payment practices.
Monitoring checks fee recipients, payload sources and bid values
The proposal’s monitoring section lists checks for fee-recipient addresses, participation in the permissionless builder market, payload sources, trusted-payment delivery and bid-value deviations. A selected bid is flagged when its value falls below the configured percentage, initially 90–95%, of the highest-value eligible bid observed by monitoring. Trusted-payment delivery is flagged when the expected trusted payment is not received in full within the applicable settlement period.
A self-built block is flagged for investigation if monitoring observes eligible external bids exceeding the configured min-bid. The proposal keeps the current min-bid guidance in place when ePBS activates, with the value to be reviewed once there is enough available mainnet data. The Fees Monitoring Dashboard will also be updated to show which track each Lido block came through.
Implementation only takes effect following the Glamsterdam upgrade on Ethereum mainnet
Existing Relay Allowed List entries may remain eligible following the ePBS transition, subject to demonstrating technical compatibility, identifiable builder participation and sufficient transparency for Lido monitoring, as long as they meet four conditions immediately following the fork. They must be registered as an in-protocol builder or relay only for registered builders, publish the builder pubkeys and indices they bid with and keep them current, have run an ePBS-compatible Builder API endpoint on Hoodi through the testnet fork, and keep public bid and delivered-payload data that Lido monitoring can consume.
New applicants, including individual builders, will follow the standard registration process and will be vetted by the Curated Module Committee (CMC) before addition to the new List. The proposal and transition will be put to a vote in November, but implementation will only take effect following the Glamsterdam upgrade on Ethereum mainnet.
Sources
- Original source Lido Research Forum research.lido.fi