Update EIP-7942: Standardize unstable block reference field as unstable_root #10828
+3
−3
Conversation
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
github-actions
bot
added
c-update
Collaborator
File
|
Tsukimarf
approved these changes
Nov 24, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Standardized the field naming for the unstable block reference to align with consensus-spec conventions and remove internal inconsistencies. The prose previously introduced a single-letter field u while the pseudocode used block.unstable; single-letter fields are atypical in the consensus specs and the value stored is a block root, so the descriptive name unstable_root is preferable. Updated Protocol Changes item 3 to use unstable_root consistently and corrected the pseudocode to set block.unstable_root = None, ensuring the name, semantics, and assignment target match throughout the document.