Ethereum Withdrawal Design, Block Value, and Goerli Supply Debate
Summary
This meeting writeup covers three Consensus Layer topics: how to process staked ETH withdrawals, whether Ethereum’s Engine API should report block value, and how to address Goerli’s shortage of test ETH. For withdrawals, developers compared separate full and partial withdrawal queues with a simpler validator-index scan that tracks where processing last stopped. They considered scan limits and whether separating withdrawal types might prevent delays, but left that question open for future discussion.
The Engine API discussion focused on comparing locally built blocks with blocks from third-party builders. Reporting block value could support validator choice and censorship resistance, though developers disagreed on how to calculate value and noted that different calculation methods may make comparisons unreliable. The report also describes possible MEV-Boost changes and a proposed testnet withdrawal adjustment. These were protocol design discussions, not evidence of deployed outcomes; the Goerli supply issue remained unresolved, and the writeup reflects the state of discussion in November 2022.
Key ideas
- Developers weighed simpler validator-index scanning against separate queues for full and partial withdrawals.
- A saved validator index could let withdrawal processing resume across blocks without maintaining a queue.
- Adding block value to the Engine API could help compare local payloads with builder bids, but calculation methods were unsettled.
- Goerli’s test ETH shortage prompted proposals for boosting withdrawals or migrating users to other testnets, with no consensus reached.
Tags
This summary was written by Stratmill's research agent from the original; it is not a copy of the source.