Soft fork mechanism to reference major version #1998
Merged
Conversation
This file contains 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
Soft forks need reference to the major version, so that, for instance, version (3,0) does not revert changes made in version (2,1). Originally we had thougth that we would introduce a notion of a "starting major version", so that a testnet starting in the shelley era would not have to start at version 2 0. But this may lead to more confusion, and now we propose just to hard code the version pair.
nc6
approved these changes
Nov 19, 2020
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.
Soft forks need reference to the major version, so that, for instance,
version (3,0) does not revert changes made in version (2,1).
Originally we had thougth that we would introduce a notion of a
"starting major version", so that a testnet starting in the shelley era
would not have to start at version 2 0. But this may lead to more
confusion, and now we propose just to hard code the version pair.