Repository navigation
Report the v23.1 activation height in getblockchaininfo - #466
Merged
Merged
Conversation
A node could not be asked for the v23.1 activation height: no RPC reported it, and a build made before the release reports the same version as the release that sets the height. getblockchaininfo now lists it under softforks as v231, in the form of a buried deployment, on a network that schedules it, and leaves it out where it is unset. No rule changes. Tested on our CI server.
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
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 lets a node tell you the v23.1 activation height: getblockchaininfo lists it under softforks once a network schedules it, and leaves it out before. Tested on our CI server; network rules stay the same.