-
-
Notifications
You must be signed in to change notification settings - Fork 43
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
add: multiproof consistency test #424
add: multiproof consistency test #424
Conversation
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.
Very nice, so this confirms that generating multiproof is bug free.
Absolutely 🙂 |
Currently investigating the g2t issue. I found another bug in the multiproof generation so we need more complete coverage: 1f8c376 |
To clarify, the PR added the following test constantine/tests/t_ethereum_verkle_ipa_primitives.nim Lines 658 to 667 in 618d8b3
to confirm that the state of the transcript matches with go-ipa. However meaning g was wrong here: constantine/constantine/commitments/eth_verkle_ipa.nim Lines 746 to 769 in 618d8b3
D is derived from committing to g(X) and then absorbed into the transcript. I'm not sure why the transcript was correct for that consistency test but it does outline that we need a more comprehensive test suite #396 |
Adds a Verkle multiproof consistency test, a continuation to addressing issue #396, implements the test https://github.com/crate-crypto/go-ipa/blob/b1e8a79/multiproof_test.go#L63-L132 as per the Verkle trie spec
Skips ipa_multi_verify because of a potential bug in
g2t
, will be addressed and fixed in successive PRs