| Commit message (Collapse) | Author | Age | Lines | SHA | |
|---|---|---|---|---|---|
| * | chore: cargo fmt | 2025-05-02 | -2/+1 | 1a2ad55 | |
| | | |||||
| * | feat(zkvms_guest_io): Output proof size | 2025-05-02 | -0/+3 | eefb57f | |
| | | | | | | | | In each zkVM we'll write the size to /tmp/proof_size and then guest_io will read that value and place it inside our metrics output. This is not the most elegant, and in certain zkVMs the file output is a part of the benchmark timing, but it will have to do. | ||||
| * | feat(zkvms_host_io): Implement new output format for zkvm/guest | 2025-05-02 | -14/+211 | 1112cce | |
| | | |||||
| * | feat(zkvms_host_io): Add json dependency | 2025-05-02 | -65/+228 | c8505d6 | |
| | | |||||
| * | chore: Update mcl-blockchain dependency | 2025-04-24 | -67/+66 | b9a899d | |
| | | | | | | | There are no package version updates. The primary difference is that RISC0 is now compiled with the unstable feature. All other hash updates come from the switch from rust-bin to fenix. | ||||
| * | fix(zkvms/zkm): Update SDK and remove hack | 2025-04-04 | -3/+3 | 7498d60 | |
| | | | | | | | | | | | Recently ZKM introduced a bug, where SNARK_SETUP would crash, but the witness would be generated. So we introduced a hack where we would run SNARK_SETUP, ignore the crash and rerun the program again, without SNARK_SETUP. Now they fixed it, so with SNARK_SETUP, the witnesses would be generated and the proving process will be done directly after. | ||||
| * | feat(zkvms/zkm): Update SDK usage, add witness generation command | 2025-04-04 | -65/+102 | 6e8dc24 | |
| | | | | | | | | We first need to generate witnesses before proving. This is done by running the binary with SNARK_SETUP=true. Currently, the command crashes right after those witnesses are generated. As a workaround, we ignore the crash and just start it normally, using the generated witnesses. | ||||
| * | feat(zkvms/zkm): Remove SDK override, Go lib build, update SDK usage | 2025-04-04 | -8/+10 | c7a0a23 | |
| | | | | | | | | Update SDK usage, according to their new methods. ZKM moved their Go library to the zkVM repo. Their updated SDK also don't require the patch. | ||||
| * | chore: Update flake.lock and Cargo.lock | 2025-04-04 | -947/+307 | 4fc242c | |
| | | |||||
| * | chore: Rust fmt | 2025-02-27 | -36/+18 | 5b82ac7 | |
| | | |||||
| * | chore: Update zkVM packages | 2025-02-26 | -135/+192 | 91fb361 | |
| | | | | | | | | | This includes: - Updating flake.lock - Updating all host and guest Cargo.toml and Cargo.lock files - Making zkvm default.nix file modifications to account for toolchain and setup changes | ||||
| * | feat(zkm/host): Use cargo patching instead of local copy of sdk | 2025-02-10 | -163/+231 | 6dc9a7f | |
| | | |||||
| * | docs(zkvms/zkm): Add detailed documentation comments | 2025-02-10 | -0/+1 | 1cb8861 | |
| | | |||||
| * | feat(zkvms/zkm): Add benchmarking capability | 2025-02-07 | -3/+7 | 3c5ec28 | |
| | | |||||
| * | feat(zkvms/zkm): Implement proper handling of public and private inputs | 2025-02-03 | -1/+6 | 73e27ae | |
| | | |||||
| * | feat(zkvms/zkm): Update Cargo.lock and use default environments | 2025-01-31 | -55/+124 | 2ea6a00 | |
| | | |||||
| * | feat(zkm): Adapt to new input type and zkvmLib | 2025-01-30 | -4/+5956 | 5de4ae0 | |
| | | |||||
| * | fix(zkvms/zkm): Lock aws-sdk-s3 version | 2025-01-28 | -0/+1 | 25a62b5 | |
| | | |||||
| * | feat(zkvms): Add zkm host | 2025-01-16 | -0/+131 | f276736 | |
 |
index : blocksense/zkVMs-benchmarks | |
| Setups and programs for zero-knowledge virtual machine benchmarking |
| Website Summary Files Commits Branches @commit @diff @stats |