-
Notifications
You must be signed in to change notification settings - Fork 1.5k
cl/beacon: resolve payload withdrawals in one place #23280
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
Open
lystopad
wants to merge
5
commits into
main
Choose a base branch
from
feature/lystopad/gloas-production-attrs
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+174
−68
Open
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
02bfdb5
cl/beacon: resolve payload withdrawals in one place
lystopad 32d6462
cl/beacon: leave the parent beacon block root off the versions that r…
lystopad a087896
cl/beacon: address review
lystopad acd5992
cl/beacon: leave withdrawals off the version that cannot carry them
lystopad 28073af
cl/beacon: let one function own which fields each version carries
lystopad 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
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
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
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.
You are right that nil does not remove the key: PayloadAttributes has no omitempty, so V1 and V2 still receive withdrawals and parentBeaconBlockRoot as null. @yperbasis reached the same point and settled the practical half of it — the engine API schemas do not forbid extra properties, and execution clients validate decoded values rather than key presence, so a null reads as absent. Geth's V1 rejects a non-nil withdrawals list, which is what this PR stops sending, and accepts nil.
So this is a wording problem rather than a defect, and the wording is fixed: the field is left unpopulated, not omitted.
Making the keys genuinely absent is a separate change in engine_types, and not a simple one — bare omitempty on Withdrawals would be wrong, because V2 and later require the empty list to be present on the wire. omitzero is the right tool, in its own PR.