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.

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

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

Merged

Conversation

holgerd77
Copy link
Contributor

This just came up in a discussion on how to populate the new beacon block root header field for the case where Cancun starts at genesis and there is no beacon block root present for the genesis block.

@holgerd77 holgerd77 requested a review from eth-bot as a code owner August 1, 2023 17:50
@github-actions github-actions bot added c-update Modifies an existing proposal s-draft This EIP is a Draft t-core labels Aug 1, 2023
@eth-bot
Copy link
Collaborator

eth-bot commented Aug 1, 2023

✅ All reviewers have approved.

@eth-bot eth-bot changed the title EIP-4788: Mention genesis block with no existing beacon block root case Update EIP-4788: Mention genesis block with no existing beacon block root case Aug 1, 2023
@eth-bot eth-bot added the a-review Waiting on author to review label Aug 1, 2023
Copy link

@Abeanna Abeanna left a comment

Choose a reason for hiding this comment

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

approved

@@ -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? 🤔

Copy link
Member

@ralexstokes ralexstokes left a comment

Choose a reason for hiding this comment

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

lgtm!

@eth-bot eth-bot enabled auto-merge (squash) August 1, 2023 19:58
Copy link
Collaborator

@eth-bot eth-bot left a comment

Choose a reason for hiding this comment

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

All Reviewers Have Approved; Performing Automatic Merge...

@eth-bot eth-bot merged commit 3ca51a1 into ethereum:master Aug 1, 2023
18 of 19 checks passed
somnathb1 added a commit to ledgerwatch/erigon that referenced this pull request Aug 2, 2023
AskAlexSharov pushed a commit to ledgerwatch/erigon that referenced this pull request Sep 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a-review Waiting on author to review c-update Modifies an existing proposal s-draft This EIP is a Draft t-core
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants