Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update EIP-4788: Mention genesis block with no existing beacon block root case #7445

Merged
merged 1 commit into from Aug 1, 2023
Merged

Update EIP-4788: Mention genesis block with no existing beacon block root case #7445

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 2 additions & 0 deletions EIPS/eip-4788.md
View file
Open in desktop
Expand Up @@ -75,6 +75,8 @@ Validity of the parent beacon block root is guaranteed from the consensus layer,

When verifying a block, execution clients **MUST** ensure the root value in the block header matches the one provided by the consensus client.

For a genesis block with no existing parent beacon block root the 32 zero bytes are used as a root placeholder.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
For a genesis block with no existing parent beacon block root the 32 zero bytes are used as a root placeholder.
For a genesis block with no existing parent beacon block root, the root consisting of 32 zero bytes should be used in the block header.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, now the old version still made it into the merged spec, was this intended? 🤔


### EVM changes

#### Block processing
Expand Down