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: Extend payload bodies with deposit and withdrawal requests #545

Merged
merged 1 commit into from
May 15, 2024

Conversation

mkalinin
Copy link
Collaborator

Introduces ExecutionPayloadBodyV2 to accommodate depositRequests and withdrawalRequests added to the payload body in Prague, this entails adding new engine_getPayloadBodiesByRangeV2 and engine_getPayloadBodiesByHashV2 methods. This PR also contains a few naming adjustments in the examples part of the schema.

@mkalinin mkalinin merged commit 03911ff into ethereum:main May 15, 2024
3 checks passed
@realbigsean
Copy link

Was talking to @mkalinin about this today. Looks like both V1 and V2 are backwards compatible and we won't want to deal with switching endpoints at the fork since they might be used during syncing for example. It probably makes sense to just extend V1.

@james-prysm
Copy link

prysm implemented v2 but not that big of a deal to go back if there's consensus on that

@MarekM25
Copy link

Was talking to @mkalinin about this today. Looks like both V1 and V2 are backwards compatible and we won't want to deal with switching endpoints at the fork since they might be used during syncing for example. It probably makes sense to just extend V1.

I agree, I think it will be better to extend V1. We added V2 methods for now

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.

None yet

6 participants