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.
The first part of this PR is #2621.
This PR proper addresses #2455. In particular, the change in computation is justified theoretically in #2455 (comment) . Comparing the log before and after this PR confirms that it does what that comment set out to do. Before, as mentioned in #2455 (comment) ,
after
Notice that the only difference is that the HFC is already informed about the hard fork in block 4479125, wich
indeed is
k
blocks after the proposal became a candidate, and hence is stable.(I think checking for
k
, rather thank + 1
is correct: if we setk = 0
, no rollback is possible at all, so the moment we see a block adopted that has the candidate in it, we know it will happen.)