EIP-7251 adds a notion of "consolidation" so that two 32 ETH validators can combine into a single validator with higher balance. See EIP-7251 for further details and motivation. The EIP currently specifies in-protocol consolidation as a consensus-layer operation, and after talking to various staking pools on mainnet, it has become clear that offering this same functionality from the execution layer is desirable. A direct way to do this is to extend EIP-7002 with a consolidation operation, just like the exit and withdrawal functionality it currently supports. From EIP-7251, the consensus layer operation looks like this: class Consolidation(Container): source_index: ValidatorIndex
4/10/2024Exclude withdrawals to fee recipient when computing a payload's value. Context mev-boost today selects the highest bid by value from a set of bids provided by connected relays in a given slot. This value represents the amount of ETH a builder transfers to a proposer in exchange for the sale of that proposer's execution block space. Relays compute this value in one of two ways, referred to as "payment schemes": PS1. The value of the last transaction in the execution payload, which must exactly match the value claimed by the builder in their submission. PS2. Comparing the balance of the fee_recipient in the post-state after the execution payload to the pre-state amount.
2/19/2024thanks to @lightclient for helpful discussions right now, most of the mev-boost ecosystem relies on the flashbots/builder software to validate block submissions at the mev-boost relay. this software is a fork of geth and this fact implies overhead of maintaining the fork especially an issue when tracking changes around devnets for hard forks, etc
7/13/2023A proposal to move mev-boost validator registrations to the "blob" space introduced as a data layer in the upcoming Cancun hard fork following EIP-4844. Abstract Using the blob space as a sequencing layer for validator registrations improves the trust assumptions around some classes of "MEV stealing" attacks which helps harden staking pool designs. Additionally, relays and validators would enjoy reduced load from processing registrations that they endure under the current mev-boost regime. Motivation Validators currently participate in the mev-boost ecosystem by making a signed message containing their block building preferences. Relays expose these preferences to builders who use them when crafting execution payloads. In turn, relays filter out builder's execution payloads if they do not respect these preferences.
7/6/2023