-
Notifications
You must be signed in to change notification settings - Fork 23
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
Improve groth16 encode API #179
Conversation
contracts/src/groth16.rs
Outdated
/// Encoding of a [Groth16Receipt][risc0_zkvm::Groth16Receipt] by prefixing it with the verifier selector, | ||
/// taken from the first 4 bytes of the hash of the verifier parameters including the Groth16 | ||
/// verification key and the control IDs that commit to the RISC Zero circuits. | ||
pub fn encode(receipt: &Groth16Receipt<ReceiptClaim>) -> Vec<u8> { |
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.
How will we recommend going from https://docs.rs/bonsai-sdk/0.9.0/bonsai_sdk/responses/struct.SnarkReceipt.html, given we still recommend using bonsai-sdk over the zkvm for production use cases?
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.
We are going rework this one based on discussion
…o capossele/improve-groth16
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.
The new method for encoding a seal on input of a Receipt
is the right direction. I don't think we should introduce a new type though. I've made some modifications and rebased this PR onto #183
Pending #185
Attempt at solving #174 and #176.
Closes #174
Closes #176