-
-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rewamp workflows on generating commitment ids #152
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #152 +/- ##
========================================
- Coverage 82.6% 76.7% -5.9%
========================================
Files 20 19 -1
Lines 2076 1710 -366
========================================
- Hits 1714 1311 -403
- Misses 362 399 +37
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These are obviously major improvements
ACK
Hi @dr-orlovsky, I found an error related with this implementation in |
@crisdut The only way to solve the issue seems to do another re-wamp. WIP. |
Fix merklization procedure
Commitment layouts and vesper description
This is the result of self-audit for the commitment ID constructions. In v0.10 we had a very non-transparent commitment workflow with multiple redundant hashing, absence of clear tagged hash structure etc. This PR linearizes commitment workflows, streamlines and simplifies related APIs.
This is consensus-breaking since generated commitments will differ.
Summary of changes: