docs: hard forks and node-to-node versioning - #2117
Merged
Merged
Conversation
dnadales
requested review from
bladyjoker,
geo2a,
jasagredo and
nfrisby
as code owners
July 10, 2026 18:01
jasagredo
reviewed
Jul 13, 2026
jasagredo
reviewed
Jul 27, 2026
dnadales
added
no changelog
skip-tests
jasagredo
approved these changes
Jul 29, 2026
dnadales
enabled auto-merge
July 30, 2026 18:08
Add an explanation doc answering whether a hard-fork release requires bumping the node-to-node version. Short answer: no. It distinguishes the several things called a "version" and shows why the network handshake version is independent of the on-chain protocol version that triggers a hard fork. Also add a glossary entry, a sidebar link, and cross-links from adding_an_era.md.
dnadales
force-pushed
the
docs/hard-forks-ntn-versioning
branch
from
August 3, 2026 12:43
9612e3d to
30c1d80
Compare
github-project-automation
Bot
moved this from 🏗 In progress
to ✅ Done
in Consensus Team Backlog
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.
New explanation page answering: does a hard-fork release require bumping the node-to-node version?
No: the block codec enables every era and tags each block with its era, so adding an era just appends an entry.
A not-yet-active era is gated by the max-major protocol-version check, not the wire version.
Also: