From d0f0942991069f556727c3920d3a49010c1b9ba0 Mon Sep 17 00:00:00 2001 From: Alex Stokes Date: Tue, 13 Jun 2023 14:11:07 -0600 Subject: [PATCH] Update EIP-4788: clarify header and validity sections Merged by EIP-Bot. --- EIPS/eip-4788.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/EIPS/eip-4788.md b/EIPS/eip-4788.md index 8225351237c9e9..72e787a6ca11d1 100644 --- 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