Enshrined Proposer-Builder Separation

The five-minute read

One action, walked through

1. Open EIP 7732 and read the status line before the examples.
2. Write down the rule in one sentence. A fair version of that sentence is: This EIP fundamentally changes the way an Ethereum block is validated by decoupling the execution validation from the consensus validation both logically as well as temporally.
3. Name the object that changes: PTC.
4. Ask what an old client, an old contract, or an offline counterparty does. If the document is silent, the silence is part of the design.

The argument, unpacked

What has to be true

• You are implementing EIP 7732 at the status the text itself states: Review.
• The object that has to change is PTC. A neighbouring document with a similar name is not this one.
• Constants in the text can be superseded by a later fork. Cite the EIP number and the fork you mean.

What happened after the paper

The source marks this review. It is not a live consensus rule just because it has a number. Later documents can narrow, replace, or ignore this one. Cite the number you mean.

What to check before you use the idea

• What does Enshrined Proposer-Builder Separation charge, reject, or redefine on the first touch versus a later one?
• Does a reverted subcall roll the change back?
• Can you point at the object in a client: PTC?

Terms

EIP 7732

The public text titled Enshrined Proposer-Builder Separation.

Review

The document's own label for how finished the text is. It is not a market fact.

The problem the paper names

An underpriced or ambiguous EVM rule is not a feature. It is a block that takes longer than the gas limit claimed, or a client that disagrees about the result.

What the design proposes

• This EIP fundamentally changes the way an Ethereum block is validated by decoupling the execution validation from the consensus validation both logically as well as temporally.
• It does so by introducing a new in-protocol entity called builders and adding a new duty (submitting payload timeliness attestations) to Ethereum validators.
• The ExecutionPayload field of the BeaconBlockBody is removed and instead it is replaced by a signed commitment (a SignedExecutionPayloadBid object) from a builder to later reveal the corresponding execution payload.

How the mechanism is specified

• Taken from the specification, the next constraint is: It does so by introducing a new in-protocol entity called builders and adding a new duty (submitting payload timeliness attestations) to Ethereum validators.
• Locate PTC in EIP 7732 and apply it to one transaction or call.
• Then check the failure the class of rule always has: a node that did not upgrade, a reverted call, a replayed signature, or a peer that does not speak the message.

What this page does not treat as proven

• A gas or opcode change is not a throughput benchmark. It is a relative price and a validity rule.
• Constants in the text can be superseded by a later fork. Cite the EIP number and the fork you mean.
• The source marks this review. It is not a live consensus rule just because it has a number.

Why a venture studio still reads it

Use EIP 7732 when a pitch says 'Enshrined Proposer-Builder Separation' without saying whether the rule is consensus, policy, or an interface. The number is the citation. The pitch is not.