Crate for verification?

[illuzen]

I'm trying to separate prover and verifier into two systems, which I believe is the canonical use case for these systems. Could you guys separate the verification code into a separate crate that cargo can import?

We can also help with that if you are open to PRs...

[illuzen]

Succinct has a very elegant setup where you just import a verifier crate and specify the proof type, feed in the proof + public inputs + verification key

    crate::Groth16Verifier::verify(&proof, &public_inputs, &vkey_hash, &crate::GROTH16_VK_BYTES)
        .expect("Groth16 proof is invalid");

https://github.com/succinctlabs/sp1/tree/dev/crates/verifier

[zah]

Are you interested specifically in a verifier for the proofs generated with the Plonky2 back-end that has been developed in this fork of Noir, or perhaps you need a verifier for regular Noir proofs (such a request may be more appropriate for the original upstream repo)?

[illuzen]

Hi @zah ! Yes specifically for plonky2, altho I think upstream noir might benefit from such a think. I managed to tease the verification out by serializing ProofWithPublicInputs, VerifierCircuitData, and CommonCircuitData with .to_bytes, then reconstituting it on the other system with from_bytes. These structs are all in the plonky2 PolygonLabs upstream, so I can just import that crate on the verifier side.

So maybe that could make the separation simpler, just make the prover output artifacts that can be verified with plonky2 alone... I can share our code if that helps, will have to separate it out and it's quite inelegant, but it works as a prototype...

[faiznaufal98]

I believe this project