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
Sometimes you'd want to actually load an external verification_key instead of initializing one from the circuit. For example, one could load it from the output json of nargo compile --include-keys.
Reason being that it's just faster than having to compute the vk in case you already have it, or you're storing it somewhere on the browser
Happy Case
I want to be able to initialize my Backend instance with a precomputed VK. Example:
Closing this as the only time it would make sense to use is when you're just verifying an externally produced proof, at which point you would use @michaeljklein's work on #3450
Prerequisite
Problem
Sometimes you'd want to actually load an external
verification_key
instead of initializing one from the circuit. For example, one could load it from the output json ofnargo compile --include-keys
.Reason being that it's just faster than having to compute the vk in case you already have it, or you're storing it somewhere on the browser
Happy Case
I want to be able to initialize my Backend instance with a precomputed VK. Example:
This would call
acirLoadVerificationKey
and load it from thecircuit.verification_key
field in the compiled circuit.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: