@ -125,37 +125,37 @@ And a inputs file `inputs.json`
In the command line, execute:
In the command line, execute:
```
```
> go-snark compile test.circuit
> go-snark-cli compile test.circuit
```
```
This will output the `compiledcircuit.json` file.
This will output the `compiledcircuit.json` file.
##### Trusted Setup
#### Trusted Setup
Having the `compiledcircuit.json`, now we can generate the `TrustedSetup`:
Having the `compiledcircuit.json`, now we can generate the `TrustedSetup`:
```
```
> go-snark trustedsetup compiledcircuit.json
> go-snark-cli trustedsetup
```
```
This will create the file `trustedsetup.json` with the TrustedSetup data, and also a `toxic.json` file, with the parameters to delete from the `Trusted Setup`.
This will create the file `trustedsetup.json` with the TrustedSetup data, and also a `toxic.json` file, with the parameters to delete from the `Trusted Setup`.
##### Generate Proofs
#### Generate Proofs
Assumming that we have the `compiledcircuit.json` and the `trustedsetup.json`, we can now generate the `Proofs` with the following command:
Assumming that we have the `compiledcircuit.json` and the `trustedsetup.json`, we can now generate the `Proofs` with the following command:
```
```
> go-snark genproofs
> go-snark-cli genproofs
```
```
This will store the file `proofs.json`, that contains all the SNARK proofs.
This will store the file `proofs.json`, that contains all the SNARK proofs.
##### Verify Proofs
#### Verify Proofs
Having the `proofs.json`, `compiledcircuit.json`, `trustedsetup.json` files, we can now verify the `Pairings` of the proofs, in order to verify the proofs.
Having the `proofs.json`, `compiledcircuit.json`, `trustedsetup.json` files, we can now verify the `Pairings` of the proofs, in order to verify the proofs.
```
```
> go-snark verify
> go-snark-cli verify
```
```
This will return a `true` if the proofs are verified, or a `false` if the proofs are not verified.
This will return a `true` if the proofs are verified, or a `false` if the proofs are not verified.