[DO NOT MERGE] Implement auto-recovery from hardforks (without fixing BLOCK_CONFLICT_CHAINLOCK flag logic) #3925
Conversation
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
UdjinM6
changed the title
UdjinM6
force-pushed
the
autorecovery_noclflag
branch
from
ab3a2d0 to
90c7b43
Compare
Author
|
Rebased to make sure it fails now. Previous build ab3a2d0: https://gitlab.com/dashpay/dash/-/pipelines/239724975 |
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.
This PR is only meant to demonstrate an undesired behaviour of "auto-recovery from hardforks"
(will push next)#3926 without implementing a proper logic forBLOCK_CONFLICT_CHAINLOCK#3924. Not to be merged.