Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update: README.md #62

Merged
merged 1 commit into from
Mar 15, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -84,13 +84,16 @@ If successfully, it will generate the binary files in `target/release`/{`sha2-ru

> 5. The environment variable `KEY_GENERATION` is set to "true", it will generate the proof key (pk), the verification key (vk) and the verifier contract and store them at the path indicated by `VERIFYING_KEY_PATH`.Then, the `KEY_GENERATION` should be set to "false" , next executing the host will generate the snark proof using the same pk and vk.

> 6. The degree bits for tables can be configured using environment variables such as `ARITHMETIC`, `CPU`, etc. For example, if the error "Error: Missing preprocessed circuits for Cpu table with size 12" appears, resolve it by running: `export CPU="12..13"`.

> [!WARNING]
> The environmental variable `SEG_SIZE` in the run_proving.sh affects the final proof generation.

> The guest program's ELF with the input is split into segments according the SEG_SIZE, based on the cycle count.

> When generating proofs on the local machine, if the log shows "[the seg_num is:1 ]", please reduce SEG_SIZE or increase the input. If generating proofs through the proof network, SEG_SIZE must be within the range [65536, 262144].

> The SEG_SIZE also affects the tables' degree bits.
### Example 1 : `sha2-rust`

This host program sends the private input pri_input = vec![5u8; 1024] and its hash (hash(pri_input)) to the guest program for verification of the hash value.
Expand Down
Loading