-
Notifications
You must be signed in to change notification settings - Fork 810
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
Verify Versioned Hashes During Optimistic Sync #4832
Merged
Merged
Changes from 7 commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
27716c0
Convert NewPayloadRequest to use Reference
ethDreamer faa9ff1
Refactor for Clarity
ethDreamer dd18fed
Verify Versioned Hashes
ethDreamer 3e78411
Added Tests for Version Hash Verification
ethDreamer 04b5f26
Added Moar Tests
ethDreamer 7aadcad
Fix Problems Caused By Merge
ethDreamer 32d3e99
Update to use Alloy Instead of Reth Crates (#14)
ethDreamer 2dddb84
Update beacon_node/execution_layer/src/engine_api/new_payload_request.rs
ethDreamer 5d5b08d
Faster Versioned Hash Extraction
ethDreamer 9cd7386
Update to rust 1.75 & Pin alloy-consensus
ethDreamer File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I notice we only do this verification when we're doing optimistic sync without the EL, yet the spec says we should always do it. I can't think of a good reason to always do it, but do we know why the spec says that?
https://github.com/ethereum/consensus-specs/blob/v1.4.0-beta.2/specs/deneb/beacon-chain.md#modified-process_execution_payload
I noticed that the execution API specs say that the EL will always verify the versioned hashes, so it seems redundant for us to do it on the CL side as well
https://github.com/ethereum/execution-apis/blob/main/src/engine/cancun.md#engine_newpayloadv3