[Bug] Fix g_best_block initialization in ABC #1457
Merged
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.
g_best_block
holds a cached best block hash.This is updated during
ActivateBestChain
(inUpdateTip
).Problem: at startup, the object is not initialized until a new block arrives (
ActivateBestChainStep
is not called) thusg_best_block != chainActive.Tip()->GetBlockHash()
so, if the client stakes before receiving a new block, that stake gets orphaned.In case of segregated devnet with just one staker, it is impossible to move the chain at all.