-
Notifications
You must be signed in to change notification settings - Fork 337
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
Bonsai: Migrate SnarkProof types to match backend #853
Conversation
Migrated to the SnarkProof + SnarkSeal model from bonsai inline with the backend changes
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.
LGTM, but mostly from a DevEx/API perspective, I'm not really able to evaluate the implementation.
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.
Definitely an improvement to code quality ❤️
I added one comment arguing the semantics of "receipt" and "proof", depending on your definition of semantics.
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.
I like this simplification!
bonsai/ethereum-relay/src/uploader/completed_proofs/complete_proof.rs
Outdated
Show resolved
Hide resolved
Update: bonsai-foundry-template ( with some update: risc0/risc0-foundry-template#58) works e2e on my end! |
Migrated to the more complete SnarkProof type from Bonsai to enable easier ETH verify integrations.
I updated most of the relay codebase to match the the new format, I hope I got everything wired up correctly but if someone who knows how to drive e2e testing with bonsai could help me validate it that would be great!.