fix: correct RFC reference from 8170 to 8174 in eip-template.md #10240
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
Contributor
VolodymyrBg
commented
Aug 29, 2025
VolodymyrBg
commented
- Change RFC 8170 to RFC 8174 in the Specification section comment
- Aligns template with EIP-1 specification and existing EIP documents
- RFC 8174 is the correct standard for terminology alongside RFC 2119
- All existing EIPs use RFC 8174, making this consistent with the codebase
github-actions
bot
added
c-update
|
🛑 |
|
will let @SamWilsn take a call on this |
3 tasks
SamWilsn
approved these changes
Sep 9, 2025
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.