-
Notifications
You must be signed in to change notification settings - Fork 40
Implement NMT multiproof verification. #131
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
Conversation
@@ -1,2 +1,3 @@ | |||
[profile.default] | |||
solc_version = "0.8.11" | |||
via_ir = true |
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.
This is needed to avoid stack too deep error. Will result in longer compile times but that should be fine since the contracts are small anyways. The QGB contract doesn't have to be re-compiled / bindings re-generated (ABI is identical).
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.
Dope 🚀
Thanks a lot for your help.
Question:
Now that we have the implementation of the multiproof, does it make sense to create a separate contract that calls it? And we generate a go wrapper for this latter so that we use it in the verification command we're planning to have for the QGB?
If so, I can create an issue and start working on it.
Fixes #128
Implements https://github.com/celestiaorg/nmt/blob/95e8313eb788b46b30f3f85b20fd9a40bf68d432/proof.go#L140.