Witness generation irrelevant?

[illuzen]

So I see that nargo execute still generates noir.gz and noir.json, but if I delete these files and run nargo prove, it works and does not regenerate those files. I assume your modifications bypass the typical flow with noir, but could you clarify what the intended workflow is for this?

My understanding is plonky2 does not require a trusted setup, so perhaps that .gz file is an artifact from that?

[nickysn]

Since the plonky2 back end is built into the compiler (i.e. it doesn't invoke a separate binary), there's no need for executing nargo execute. Instead, you can invoke nargo prove directly, because it compiles and executes the program as a first step. nargo verify also compiles the program, however, it does not execute it, as it is not necessary for the verification.

[illuzen]

Hi @nickysn thank you that clears things up.

We are seriously considering using this in production. The main todos for us are

• Separation of Verifier so that verifier can just run PolygonLabs/plonky2 and not touch noir
• Separation of Prover so it can be imported into a mobile app
• Getting a security audit

Is this something your team would support or accept as a PR or should we fork?

[zah]

We'll be happy to review and potentially accept PRs for these developments. We would love to see our toolkits being used in production by other teams, especially ones that contribute improvements.