Update EIP-4788: clarify header and validity sections

Merged by EIP-Bot.
ethereum · Jun 13, 2023 · d0f0942 · d0f0942 · HAAH10 · Aug 29, 2023
1 parent 6f84674
commit d0f0942
Showing 1 changed file with 3 additions and 4 deletions.
diff --git a/EIPS/eip-4788.md b/EIPS/eip-4788.md
@@ -40,11 +40,10 @@ To bound the amount of storage this construction consumes, a ring buffer is used
 
 ### Block structure and validity
 
-Beginning at the execution timestamp `FORK_TIMESTAMP`, execution clients **MUST**:
+Beginning at the execution timestamp `FORK_TIMESTAMP`, execution clients **MUST** extend the header schema with an additional field: the `parent_beacon_block_root`.
+This root consumes 32 bytes and is exactly the [hash tree root](https://github.com/ethereum/consensus-specs/blob/fa09d896484bbe240334fa21ffaa454bafe5842e/ssz/simple-serialize.md#merkleization) of the parent beacon block for the given execution block.
 
-1. set 32 bytes of the execution block header after the last header field as of `FORK_TIMESTAMP` to the 32 byte [hash tree root](https://github.com/ethereum/consensus-specs/blob/fa09d896484bbe240334fa21ffaa454bafe5842e/ssz/simple-serialize.md#merkleization) of the parent beacon block.
-
-*NOTE*: this field is appended to the current block header structure with this EIP so that the size of the header grows after (and including) the `FORK_TIMESTAMP`.
+Validity is guaranteed from the consensus layer, much like how withdrawals are handled.
 
 ### EVM changes