Skip to content

Commit

Permalink
typos README.md (#347)
Browse files Browse the repository at this point in the history
  • Loading branch information
Dimitrolito authored Dec 16, 2024
1 parent f708787 commit d165113
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion prover/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ To generate a proof that a computation was executed correctly, you will need to
1. Define *algebraic intermediate representation* (AIR) for your computation. This can be done by implementing `Air` trait (see [air crate](../air) for more info).
2. Define an [execution trace](#Execution-trace) for your computation. This can be done by implementing `Trace` trait. Alternatively, you can use `TraceTable` struct which already implements `Trace` trait in cases when this generic implementation works for your use case.
3. Execute your computation and record its execution trace.
4. Define your prover(#Prover) by implementing `Prover` trait. Then execute `Prover::prove()` function passing the trace generated in the previous step into it as a parameter. The function will return a instance of `Proof`.
4. Define your prover(#Prover) by implementing `Prover` trait. Then execute `Prover::prove()` function passing the trace generated in the previous step into it as a parameter. The function will return an instance of `Proof`.

The resulting `Proof` object can be serialized and sent to a [verifier](../verifier) for verification. The size of proof depends on the specifics of a given computation, but for most computations it should be in the range between 15 KB (for very small computations) and 300 KB (for very large computations).

Expand Down

0 comments on commit d165113

Please sign in to comment.