Agenda
EIP-7732 breakout room #9 · Issue #1150 · ethereum/pm · GitHub
Notes
Notes by @terence [copied from X]
- Julian presented an argument that slot auction gives an out-of-protocol trusted advantage by running an MEV-Boost auction at the execution stage
- Mark presented new engine API methods for retrieving payloads
- We talked about whether withdrawals could be on executions and what the blocker for this is
Recap by @potuz [copied from Eth R&D Discord]
- @JulianMa presented an analysis pretty much showing that on slot auctions there’s a “trusted advantage” that does not seem to be possible to avoid. This seems like a serious problem on slot auctions and it’d be nice to weigh against the known problems of block auctions. We decided to keep building on block auctions for the time being cause it’s an easy switch to slot auctions if they are decided later.
- @ethDreamer proposed a new method in the Engine API to requests payloads by range. We agreed that it was sensible to have this method. I raised that we shouldn’t even need to have the payload to sync. Would like to talk to @m.kalinin about this, Perhaps we can schedule an informal call Misha? I think once the requests are sent outside of the payload and the block is hashed as SSZ, we should not need to get the payloads ever on the CL, and would only need to have the payload HTR.
- @terence proposed that we moved the processing of withdrawals to the execution phase. Mark seemed to strongly prefer it, I don’t oppose it and even like it, but acknowledge that it’s different on the beacon chain and would want someone else besides me vouching for it. We decided to requests here for signals from teams if they rather want to move this to the EL payload processing.
Recording
