Merklize commitment tree anchor keys #3125
Merged
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
grarco
added
the
breaking:consensus
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #3125 +/- ##
=======================================
Coverage 59.39% 59.40%
=======================================
Files 298 298
Lines 92771 92780 +9
=======================================
+ Hits 55104 55116 +12
+ Misses 37667 37664 -3 ☔ View full report in Codecov by Sentry. |
Closed
brentstone
added a commit
that referenced
this pull request
Apr 24, 2024
* grarco/merkle-masp-hashes: Fixes merkle unit tests Changelog #2794 Tests masp keys merklization Merklize the masp commitment tree anchor keys
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.
Describe your changes
Closes #2794.
Adds the masp commitment tree anchor keys to the merkle tree so that they can be tracked in the app hash.
Indicate on which release or other PRs this topic is based on
v0.33.0
Checklist before merging to
draft