Correction for spork key update - #45
Merged
Merged
Conversation
…d activation window; doc update; v3.4.2.11
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
1 participant
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.
Bug Hot-Fix
This PR is to correct the update process for the spork key change. This is required due to the failure of the spork key change in the prior versions.
The [new] spork key change will begin in approximately one week from this commit.
Process Change Details
At height
755040theV2spork keys will be used. At block height775000theV3spork keys will then be used, and the spork key changes will then be enforced. Any mismatching nodes/peers will be banned, at height775200and beyond.