Regarding the FAQ on preventing MEV by Proposers, I’m having trouble fully understanding the concept and would like to confirm my understanding.
What prevents block proposers from stealing MEV from submitted builders’ blocks?
If my understanding correct, the following steps are taken to prevent MEV stealing by Proposers.
① The Proposer retrieves the blindBlock using getHeader.
② When the Proposer receives that block, they sign the header.
③ The signed data is sent to the ExecutionClient or Consensus Client.
④ Based on the signed data, the full block is retrieved using submitBlindedBlock.
⑤ The full block is submitted. If the header differs from the one in ③, they are slashed.
Is my understanding of ③ correct?
Also, if it is, could someone explain which specific API is used and what it does?
I would greatly appreciate any insights.
These docs should clarify:
The API for (3) is getPayload, where the proposer sends the signed blinded beacon block to the relay, at which point the block will be proposed by the relay.
@metachris Thank you!
- The builder running the Builder API is expected to respond with the full execution payload upon seeing the blinded block proposal. This allows the validator to create a “signed” Beacon block, which they propagate throughout the network.
- A validator using the Builder API is still expected to build a block locally in case the block builder fails to respond promptly, so they don’t miss out on block proposal rewards. However, validator cannot create another block using either the now-revealed transactions or another set, as it would amount to equivocation (signing two blocks within the same slot), which is a slashable offense.
I initially thought that the “sign” by the proposer simply involved signing the header with a private key and then sending that signed data to the builder.
However, after looking at ethereum.org, I’ve come to understand that the signed block header is created within the consensus client, and that data is then transmitted.