You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Once upon a time, in PR #3322 , there was this comment:
// The "real" workflow will involve a prover and a verifier on different systems.
//
// We cannot do this in our tests because they will panic with:
// `unreachable`
//
// This happens when we we create a proof with one barretenberg instance and
// try to verify it with another.
//
// If this bug is fixed, we can remove this test and split barretenberg into
// a prover and verifier class to more accurately reflect what happens in production.
Since that PR fixed the bug, seems like we can tackle this now, just as @TomAFrench suggested
Happy Case
backend_barretenberg has two classes, one for proving and one for verification
Alternatives Considered
No response
Additional Context
No response
Would you like to submit a PR for this Issue?
No
Support Needs
No response
The text was updated successfully, but these errors were encountered:
@kevaundray Is this something that we want to pursue? Seems like we're going to end up paying the fixed costs associated with bb.js twice for not much benefit.
…4769)
# Description
## Problem\*
Resolves#3450
## Summary\*
- In order to prove + verify, we have proving and verification keys
+ The proving key is derived from the circuit representation and the
verification key is derived from the proving key
+ The proving key is generally quite big, so we always generate it from
the circuit, which is easier than lugging it around
+ The verification key is much smaller and can be compressed
- Ideally, a user verifying a proof should be able to simply send the
verification key and proof to BB
## Additional Context
## Documentation\*
Check one:
- [x] No documentation needed.
- [ ] Documentation included in this PR.
- [ ] **[For Experimental Features]** Documentation to be submitted in a
separate PR.
# PR Checklist\*
- [x] I have tested the changes locally.
- [x] I have formatted the changes with [Prettier](https://prettier.io/)
and/or `cargo fmt` on default settings.
---------
Co-authored-by: TomAFrench <[email protected]>
Co-authored-by: Tom French <[email protected]>
Problem
Once upon a time, in PR #3322 , there was this comment:
Since that PR fixed the bug, seems like we can tackle this now, just as @TomAFrench suggested
Happy Case
backend_barretenberg
has two classes, one for proving and one for verificationAlternatives Considered
No response
Additional Context
No response
Would you like to submit a PR for this Issue?
No
Support Needs
No response
The text was updated successfully, but these errors were encountered: