eigencloud

verifiable cloud arc ☁️

verifiable cloud szn ☁️

verifiable cloud era ☁️

@eigencloud

Verify anything. Create apps and agents with trust built-in.

Join the conversation → /eigencloud

public goods maxi. accelerating @eigencloud. 🌱 investing in consumer apps @socialgraphvc. gratitude journal /pratik.  🦁 @safary. ♥️ national parks

Tricks with polynomials and Riemann-Roch spaces. Breaking into the platonic realm to pillage forbidden abstractions. Starknet grantee.

honestly good defaults for some of the flags would go a long way. This is the current workflow if you want to compile a circuit, generate a proof, generate the verifying key and verify the proof:
- `nargo check` checks that your circuit will compile and generate a Prover.toml file where you put your witness.
- `nargo execute` on project root. This solves the circuit's witness, creates a `./target/` dir and saves it there.
- `bb prove -b ./target/circuit.json -w ./target/circuit.gz -o ./target` wait wtf is bb?! You were starting to get comfortable with nargo so fuck that now you need to use a different binary called `bb` it's short for barratenberg. Who knows what the name stands for but it's an elliptic curve library for the bn128 curve, and a PLONK SNARK prover. So you call the `prove` command on the `bb` cli and pass the `-b` flag pointing it to your circuit's binary which we just created with `nargo execute`. We also pass the `-w` flag to point to the witness that was also just created. Finally, we pass the `-o` flag to point bb to where we want it to save the proof. Proof saved to `./target/proof`
- Now that we have the proof we want to verify it locally just to test that it works: `bb write_vk -b ./target/circuit.json -o ./target` we call the `write_vk` command, pass the -b flag pointing to our binary again and specify the output target with -o again. VK saved to `./target/vk`
- Cool, we now have everything we need to verify our circuit's proof given the witness: `bb verify -k ./target/vk -p ./target/proof` call bb with the `verify` command, pass the -k flag pointing to the verifying key, pass the -p command pointing to the proof. Proof verified successfully, cool.

You should connect with francos.eth, who said: 'Honestly good defaults for some of the flags would go a long way. This is the current workflow if you want to compile a circuit, generate a proof, generate the verifying key and verify the proof...' Join the conversation in the /zk channel.