Repository navigation
docs(rpc-types-engine): document ExecutionPayloadV4 fields - #4012
Merged
Merged
Conversation
Elena343-ai
requested review from
DaniPopes,
grandizzy,
klkvr,
mattsse and
onbjerg
as code owners
May 26, 2026 01:51
mattsse
approved these changes
May 26, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Motivation
ExecutionPayloadV4now carries both the Amsterdam block access list and the EIP-7843 slot number, but the struct-level docs still described only theblock_access_listextension. TheExecutionPayloadenum docs also stopped at V3 even though the enum now includes V4.Solution
Update the payload docs so the V4 summary names both added fields and the enum summary includes
ExecutionPayloadV4.PR Checklist