Update EIP-8016: Link first references to EIP-7916 and EIP-7495 #10803
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
|
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.
This change adds relative links to ./eip-7916.md and ./eip-7495.md on the first mentions of ProgressiveList[type] and ProgressiveContainer(active_fields) in the “Compatible Merkleization” list of EIP-8016. EIP-1 requires that the first reference to another EIP be linked with a relative path, and bringing these inline ensures editorial compliance, improves navigability for readers, and avoids ambiguity about the referenced definitions. The modification is strictly editorial and does not alter any normative content or semantics of the proposal.