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
Currently nargo always generates a proof in ${monorepoRoot}/proofs/${packageName}.proof.
This does not work for server side applications that generate multiple proofs in parallel as they can override each other. nargo prove command already allows to specify Prover.toml & Verifier.toml names. Proof name should also be configurable
Problem
Currently
nargo
always generates a proof in${monorepoRoot}/proofs/${packageName}.proof
.This does not work for server side applications that generate multiple proofs in parallel as they can override each other.
nargo prove
command already allows to specifyProver.toml
&Verifier.toml
names. Proof name should also be configurableHappy Case
nargo prove --proof-path ../custom_proofs/uuid.proof
Project Impact
Blocker
Impact Context
Without it - each proof needs to be generated in a separate file system or all proofs need to be generated sequentially
Workaround
Yes
Workaround Description
Kinda. As described above
Additional Context
No response
Would you like to submit a PR for this Issue?
None
Support Needs
No response
The text was updated successfully, but these errors were encountered: