# Example: TestCircuit in IR

We describe how the full workflow working with the test circuit given in circuit.rs:465.

First, the IR file is as follows.

// circuit.pir
range[2^6] a
range[2^5] b
pub c = a + b
pub d = a * b
pub f = (fixed_base_scalar_mul e)


Above, we have to use "(...)" to force a gate expression in the current grammar since it is vague to the parser what is a gate vs what is a poly.

Note that the base for the gate fixed_base_scalar_mul is fixed to be generator by the backend, where


#![allow(unused)]
fn main() {
let (x, y) = P::AFFINE_GENERATOR_COEFFS;
let generator = GroupAffine::new(x, y);
}


## Compile

To compile, we can run

pir compile circuit.pir -op circuit.prover.bin -ov circuit.verifier.bin


The two binary files stores the necessary data and metadata for the prover and the verifier.

### Output wires

During compilation, the backend should realize that wires c, d, f are output wires, meaning they are derivable given values of a, b, e.

## Proof generation

Since the only non-output wires are a, b, e, one should be able to generate a proof by specifying the following two JSON files.

The public input table PI.json is actually empty, since all public wires are output wires and can be computed by the backend during prover runtime.

// PI-prover.json
{}


The witness input table W.json contain values for a, b, and e.

// W.json
{
"a": 20,
"b": 5,
"e": 2
}


To generate a proof, we run

pir proof circuit.prover.bin PI W --proof proof.bin --PI PI-verifier.json


The above command should (1) generate a binary file containing the Plonk proof and (2) generate a table pubout.json.

Table PI-verifier.json should now contain the computed values of c, d, f.

// PI-verifier.json, after proof generation
{
"c": 25,
"d": 100,
"f": .. // representation of the group element 2 * g, where g is the fixed base
}


## Proof verification

To verify a proof, we can run the following command to determine the validity of a proof.

pir verify circuit.verifier.bin PI-verifier.json proof.bin