server: Respect option to allow old forks.#3639
Merged
davecgh merged 1 commit intodecred:masterfrom Mar 10, 2026
Merged
Conversation
davecgh
force-pushed
the
server_respect_oldforks_option
branch
from
0f0f90a to
24a3d4d
Compare
jholdstock
approved these changes
Mar 9, 2026
The option to allow old forks is currently not being set in the blockchain config as it should be, so the behavior is only being activated when the assume valid hash is 0 as opposed to when either case is true. This corrects that by setting the flag in the blockchain config as intended.
davecgh
force-pushed
the
server_respect_oldforks_option
branch
from
24a3d4d to
acff9bd
Compare
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
2 participants
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 option to allow old forks is currently not being set in the blockchain config as it should be, so the behavior is only being activated when the assume valid hash is 0 as opposed to when either case is true.
This corrects that by setting the flag in the blockchain config as intended.