Move EL requests to BeaconBlockBody #6435
Closed
Conversation
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
pawanjay176
added
work-in-progress
pawanjay176
force-pushed
the
engine-requests
branch
from
620ca10
to
c823f63
Compare
|
Merging this PR to #6445 to consolidate all alpha 6 spec changes |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Issue Addressed
N/A
Proposed Changes
Move all EL requests from the
ExecutionPayloadtoBeaconBlockBodyaccording to ethereum/consensus-specs#3875 . Modify engine api to support the changes.Engine api changes are not yet merged.
The direction seems to be removing.ExecutionPayloadBodyV2and moving requests fromJsonExecutionPayloadV4toJsonGetPayloadResponse(ethereum/execution-apis#587) and changing requests to an opaque ssz bytes container (ethereum/execution-apis#577) in the json objectThe engine api changes are here ethereum/execution-apis#591