As depicted above and described in the Builder — Honest Validator repository, the MEV-Boost block proposal process begins with a registration step that validators must perform ahead of proposal duties. Registration ensures builders can craft blocks for a given validator’ block proposal. Once registered, validators wait until selected to propose a block. Once selected, a block proposer building a block on top of a beacon
state in a given
slot must take the following actions to obtain an execution payload:
- Users/searchers send transactions to block builders through public or private peer-to-peer transaction pools.
- Builders construct execution payloads using received transactions, and parameters the block proposer provided during registration. To process MEV payment, builders set their own address as the payload’s coinbase address and append a transaction to the block proposers’ feeRecipient address at the end of their proposed block. The block is then forwarded to relays.
- Relays verify the validity of payloads (including amount of ETH paid to the block proposers’ feeRecipient), and send an
ExecutionPayloadHeader(execution payloads stripped of transaction content) to MEV-Boost. MEV-boost selects the most valuable payload and forwards it to the block proposer.
- The block proposer signs the payload and passes it back to MEV-Boost via a
submitBlindedBlockcall, which is forwarded to the relay. Once the relay verifies the proposers’ signature, it responds with the full execution payload body for the validator to use when proposing a
SignedBeaconBlockto the network.