Update doc to add 'cargo-zisk rom-setup' command (#311)

* Update doc: added rom-setup command

* Fix rom-setup command flags

Author: agnusmor

book/getting_started/installation.md

@@ -125,7 +125,6 @@ You can use the flags `--provingkey`, `--verifykey` or `--nokey` to specify the
     2. Build and install the Rust ZisK toolchain:
     ```bash
     cargo-zisk sdk build-toolchain
-    ZISK_TOOLCHAIN_SOURCE_DIR=. cargo-zisk sdk install-toolchain
     ```
 
 6. Verify the installation:
@@ -204,8 +203,13 @@ Please note that the process can be long, taking approximately 2–3 hours depen
     ```
 
 ## Uninstall Zisk
-To uninstall ZisK, run:
 
-```bash
-rm -rf $HOME/.zisk
-```
+1. Uninstall ZisK toolchain:
+    ```bash
+    rustup uninstall zisk
+    ```
+
+2. Delete ZisK folder
+    ```bash
+    rm -rf $HOME/.zisk
+    ```

book/getting_started/quickstart.md

@@ -10,7 +10,6 @@ Ubuntu 22.04 or higher is required.
 
 > **Note:** macOS is not yet supported, but we are actively working on adding support.
 
-1. Make sure you have [Rust](https://www.rust-lang.org/tools/install) installed.
 1. Make sure you have [Rust](https://www.rust-lang.org/tools/install) installed.
 
 2. Install all required dependencies with:
@@ -101,15 +100,21 @@ cargo-zisk run --release -i build/input.bin
 
 ## Prove
 
-You can generate and verify a proof using the `cargo-zisk prove` command by providing the ELF file (with the `-e` or `--elf` flag) and the input file (with the `-i` or `--input-data` flag).
+Before generating a proof, you need to generate the program setup files. Execute:
+
+```bash
+cargo-zisk rom-setup -e target/riscv64ima-polygon-ziskos-elf/release/sha_hasher
+```
+
+Once the program setup is complete, you can generate and verify a proof using the `cargo-zisk prove` command by providing the ELF file (with the `-e` or `--elf` flag) and the input file (with the `-i` or `--input` flag).
 
 To generate and verify a proof for the previously built ELF and input files, execute:
 
 ```bash
 cargo-zisk prove -e target/riscv64ima-polygon-ziskos-elf/release/sha_hasher -i build/input.bin -o proof -a -y
 ```
 
-This command generates the proof in the `./proof directory`. If everything goes well, you will see a message similar to:
+This command generates the proof in the `./proof` directory. If everything goes well, you will see a message similar to:
 
 ```
 ...

book/getting_started/writing_programs.md

@@ -224,12 +224,33 @@ bd13089b
 
 ## Prove
 
+### Program Setup
+
+Before generating a proof (or verifying the constraints), you need to generate the program setup files. This must be done the first time after building the program ELF file, or any time it changes:
+
+```bash
+cargo-zisk rom-setup -e target/riscv64ima-polygon-ziskos-elf/release/sha_hasher -k $HOME/.zisk/provingKey
+```
+In this command:
+
+* `-e` (`--elf`) specifies the ELF file localtion.
+* `-k` (`--proving-key`) specifies the directory containing the proving key. This is optional and defaults to `$HOME/.zisk/provingKey`.
+
+The program setup files will be generated in the `cache` directory located at `$HOME/.zisk`
+
 ### Verify Constraints
-Before to generate a proof (that can take some time) you can verify that all the constraints are satisfied:
+
+Before generating a proof (which can take some time), you can verify that all constraints are satisfied:
 
 ```bash
 cargo-zisk verify-constraints -e target/riscv64ima-polygon-ziskos-elf/release/sha_hasher -i build/input.bin -w $HOME/.zisk/bin/libzisk_witness.so -k $HOME/.zisk/provingKey
 ```
+In this command:
+
+* `-e` (`--elf`) specifies the ELF file localtion.
+* `-i` (`--input`) specifies the input file location.
+* `-w` (`--witness`) specifies the location of the witness library. This is optional and defaults to `$HOME/.zisk/bin/libzisk_witness.so`.
+* `-k` (`--proving-key`) specifies the directory containing the proving key. This is optional and defaults to `$HOME/.zisk/provingKey`.
 
 If everything is correct, you will see an output similar to:
 
@@ -249,8 +270,9 @@ cargo-zisk prove -e target/riscv64ima-polygon-ziskos-elf/release/sha_hasher -i b
 In this command:
 
 * `-e` (`--elf`) specifies the ELF file localtion.
-* `-i` (`--inputs`) specifies the input file location.
-* `-w` (`--witness`) and `-k` (`--proving-key`) are used to specify the location of the witness library and proving key files required for proof generation; they are optional, set by default to the paths found in the `$HOME/.zisk` installation folder.
+* `-i` (`--input`) specifies the input file location.
+* `-w` (`--witness`) specifies the location of the witness library. This is optional and defaults to `$HOME/.zisk/bin/libzisk_witness.so`.
+* `-k` (`--proving-key`) specifies the directory containing the proving key. This is optional and defaults to `$HOME/.zisk/provingKey`.
 * `-o` (`--output`) determines the output directory (in this example `proof`).
 * `-a` (`--aggregation`) indicates that a final aggregated proof (containing all generated sub-proofs) should be produced.
 * `-y` (`--verify-proofs`) instructs the tool to verify the proof immediately after it is generated (verification can also be performed later using the `cargo-zisk verify` command).