fix!: burned commitment mmr calculation and cucumber prune mode #4453
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.
mmr header calculation for burned outputs
Fix cucumber prune mode
Description
Fixes the MMR root calculation for burned commitments. They were calculated correctly in the database and prune mode sync, but not during header sync calculation.
Fixes pruned mode cucumber tests. Consensus values between local net and Esmeralda were not matching.
Reduces local net header version back to 0 to match Esmeralda version.
How Has This Been Tested?
Unit and cucumber tests
fixes: #4360
fixes: #4443