Fix utreexo roots matching #284
Merged
Conversation
This file contains 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
m-kus
force-pushed
the
m-kus/utreexo-fixups
branch
from
305f626 to
eae5664
Compare
m-kus
force-pushed
the
m-kus/utreexo-fixups
branch
from
eae5664 to
0b5f8eb
Compare
m-kus
force-pushed
the
m-kus/utreexo-fixups
branch
from
0b5f8eb to
85b004e
Compare
maciejka
approved these changes
Oct 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 changes the order in which Utreexo roots are matched for verification (Utreexo state keeps them in a "reversed" order). All integration/unit tests pass now.