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

Engine API: validate blob versioned hashes #407

Merged
merged 5 commits into from
May 24, 2023
Merged

Engine API: validate blob versioned hashes #407

merged 5 commits into from
May 24, 2023

Conversation

mkalinin
Copy link
Collaborator

Adds blob versioned hashes as a second parameter to engine_newPayloadV3 as a follow up to ethereum/consensus-specs#3345 (comment)

Co-authored-by: g11tech <develop@g11tech.io>
Copy link
Contributor

@g11tech g11tech left a comment

Choose a reason for hiding this comment

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

looks good here 👍

@mkalinin mkalinin marked this pull request as ready for review May 17, 2023 11:55
@mkalinin
Copy link
Collaborator Author

More detailed steps to validate blob versioned hashes are added, with the requirement to run this check instantly disregarding the sync process, i.e. in the same way as block hash is validated today.

This PR adds a second parameter to the newPayloadV3. An alternative is to add new ExecutionPayloadRequestV1 container and pass a payload and an expected array of blob hashes inside of this object. I would like to double check that client devs are fine with adding a second parameter vs adding a new container.

Co-authored-by: Alex Stokes <r.alex.stokes@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants