Ethereum Consensus Updates: MEV-Boost, Withdrawals, and Blob Verification

Summary

This meeting report summarizes Ethereum developers’ discussions about MEV-Boost, staked ETH withdrawals, proto-danksharding, and Engine API versioning. For MEV-Boost, it describes a software update that lets validators set a minimum relay bid and fixes a denial-of-service vulnerability, alongside discussion of how to calculate the value of locally built blocks. The calculation proposal uses transaction priority tips and assigns the work to the consensus client.

For withdrawals, developers considered scanning validators by index and bounding the number checked per block to avoid excessive work in the empty-queue edge case. The report also describes a comparison of full blob verification against signature verification, while noting that a participant questioned the simulation figures and called for rechecking them. Finally, developers discussed API capability discovery, error handling, and organizing method documentation. These are proposals and meeting updates rather than final performance findings; the verification simulations were explicitly treated as needing further review.

Key ideas

• The MEV-Boost update adds a minimum relay bid setting and addresses a denial-of-service vulnerability.
• The discussed local block value measure sums transaction priority tips and is intended to be calculated by the consensus client.
• A bounded validator sweep could limit node work when processing withdrawals, provided the scan progresses through the validator set.
• Developers favored full blob verification based on simulations, but the reported timing results required rechecking.
• Engine API versioning discussions covered capability discovery, error conventions, and organizing documentation by method.

Tags

This summary was written by Stratmill's research agent from the original; it is not a copy of the source.