| Commit message (Collapse) | Author | Age | Lines | SHA | |
|---|---|---|---|---|---|
| * | fix(zkvms/zkwasm): Change default output paths to /tmp | 2025-05-05 | -5/+5 | b75f2fb | |
| | | |||||
| * | chore: cargo fmt | 2025-05-02 | -26/+75 | 1a2ad55 | |
| | | |||||
| * | feat(zkvms_guest_io): Output proof size | 2025-05-02 | -3/+37 | 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 | -79/+1332 | 1112cce | |
| | | |||||
| * | feat(zkvms_host_io): Add json dependency | 2025-05-02 | -428/+1958 | c8505d6 | |
| | | |||||
| * | feat(zkvms/risc0): Use unstable feature | 2025-04-24 | -3/+9 | 406848b | |
| | | |||||
| * | chore: Update mcl-blockchain dependency | 2025-04-24 | -503/+664 | 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/zkwasm): Explicit type in argument | 2025-04-23 | -1/+1 | 3d7b895 | |
| | | | | | | In certain cases, we would get errors that the "x" type cannot be inferred. | ||||
| * | fix(zkvms/zkm): Include string in guest wrapper | 2025-04-23 | -1/+1 | 8b7eae6 | |
| | | |||||
| * | feat(guests/keccak): Add ZKM precompile function call | 2025-04-14 | -0/+3 | c87a637 | |
| | | |||||
| * | fix(zkvms): Fix non-braced usages of grouped methods | 2025-04-07 | -4/+4 | 1f3ca1f | |
| | | | | | | | Before grouping transformed vec![a,b,...] into "(a,b,...)", but with FunctionDefinition, grouping transforms vec![a,b,...] into "a,b,...". This change wasn't reflected in Nexus and ZKM | ||||
| * | feat(zkvms/zkwasm); Update to use FunctionDefinition | 2025-04-07 | -16/+6 | 2fcec28 | |
| | | |||||
| * | feat(zkvms/zkm): Update to use FunctionDefinition | 2025-04-07 | -21/+5 | ef33084 | |
| | | |||||
| * | feat(zkvms/sp1): Update to use FunctionDefinition | 2025-04-07 | -17/+17 | 155f577 | |
| | | |||||
| * | feat(zkvms/risc0): Update to use FunctionDefinition | 2025-04-07 | -20/+17 | 3ea60f8 | |
| | | |||||
| * | feat(zkvms/jolt): Update to use FunctionDefinition | 2025-04-07 | -21/+417 | a6c3fcf | |
| | | |||||
| * | feat(zkvms/nexus): Update to use FunctionDefinition | 2025-04-07 | -14/+7 | fef25f2 | |
| | | |||||
| * | fix(zkvms/zkm): Update SDK and remove hack | 2025-04-04 | -6/+4 | 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. | ||||
| * | chore: Nix and Rust fmt | 2025-04-04 | -18/+23 | ff02260 | |
| | | |||||
| * | feat(zkvms/zkm): Update SDK usage, add witness generation command | 2025-04-04 | -65/+105 | 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/risc0): Implement elf encoding | 2025-04-04 | -1/+29 | a30b402 | |
| | | | | | | | | | | Recently, RISC0 have added code to their SDK which adds magic bytes to the (already compiled) ELF. Since we're taking another route than intended, we'll need to replicate this step too. We're doing things in a different fashion, because their SDK normally compiles the guest, and doesn't allow you to supply a prebuilt ELF. | ||||
| * | feat(zkvms/risc0): Upper bound for bytemuck_derive | 2025-04-04 | -15/+17 | 696e604 | |
| | | |||||
| * | feat(zkvms/nexus): Update SDK usage | 2025-04-04 | -67/+30 | e701885 | |
| | | | | | Update according to their new methods. | ||||
| * | feat(zkvms/zkm): Remove SDK override, Go lib build, update SDK usage | 2025-04-04 | -84/+12 | 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. | ||||
| * | feat(zkvms/jolt): Add libcxx and openssl dependencies, upper bound for ↵ | 2025-04-04 | -7/+8 | 2c82f0f | |
| | | | | | bytemuck_derive | ||||
| * | chore: Update flake.lock and Cargo.lock | 2025-04-04 | -4326/+2494 | 4fc242c | |
| | | |||||
| * | chore(flake.nix): Replace rust-overlay with fenix | 2025-04-04 | -5/+13 | d02aef5 | |
| | | | | | This follows the same change which was made in mcl-blockchain | ||||
| * | feat(zkvms/zkwasm): Support non-numeric types as guest function output | 2025-03-05 | -25/+34 | 94115de | |
| | | |||||
| * | feat(zkvms/zkwasm): Export macro which converts to bytes vector as a library | 2025-03-05 | -112/+130 | 776f0b6 | |
| | | |||||
| * | fix(zkvms/jolt/host): Replace default formatting with debug formatting in print | 2025-03-04 | -2/+2 | b2635c1 | |
| | | |||||
| * | chore: Rust fmt | 2025-02-27 | -224/+301 | 5b82ac7 | |
| | | |||||
| * | chore: Nix fmt | 2025-02-27 | -251/+142 | 39ec264 | |
| | | |||||
| * | feat: Add zkvm cargo features | 2025-02-26 | -1/+1 | aaedf9d | |
| | | | | | So you can make code modifications compile-time, based on the zkVM | ||||
| * | fix(zkvms/zkm): Downgrade host toolchain | 2025-02-26 | -0/+3 | ec0bc2c | |
| | | | | | | | | The newest toolchain causes errors, an issue has been filed upstream: https://github.com/zkMIPS/toolchain/issues/4 However, it is not certain when it will be resolved, so for now this workaround will be used. | ||||
| * | fix(zkvms/zkm): Override zkm SDK | 2025-02-26 | -0/+52 | 4bba003 | |
| | | | | | | | | The SDK is out of date. A PR is opened: https://github.com/zkMIPS/zkm-project-template/pull/54 However, its not certain it will be merged soon, so for now this workaround will have to do. | ||||
| * | chore: Update zkVM packages | 2025-02-26 | -2067/+1358 | 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 | ||||
| * | fix(zkvms/README): Squash typos | 2025-02-13 | -1/+1 | 3d8e153 | |
| | | |||||
| * | feat(zkvms): Add README | 2025-02-13 | -0/+57 | 32a586b | |
| | | |||||
| * | feat(zkvms): Change package versions from infdev to the corresponding zkVM ↵ | 2025-02-11 | -6/+6 | 50029c0 | |
| | | | | | versions | ||||
| * | feat(zkm): Remove copy of sdk | 2025-02-10 | -2210/+0 | 0baed21 | |
| | | |||||
| * | feat(zkm/default.nix): Use repository instad of local copy of sdk for ↵ | 2025-02-10 | -5/+13 | 01b1997 | |
| | | | | | libsnark Go module | ||||
| * | feat(zkm/host): Use cargo patching instead of local copy of sdk | 2025-02-10 | -163/+231 | 6dc9a7f | |
| | | |||||
| * | fix: Delete unused old input file | 2025-02-10 | -6/+0 | 6dcc8ec | |
| | | |||||
| * | fix(zkvms/risc0): Revert changes to benchmark only the relevant function calls | 2025-02-10 | -24/+20 | 6a310e1 | |
| | | |||||
| * | fix(zkvms/risc0): Move prove output from journal message to benchmarkable scope | 2025-02-10 | -2/+1 | 85d0044 | |
| | | |||||
| * | docs(zkvms/zkwasm): Add detailed documentation comments | 2025-02-10 | -1/+65 | 35dc06a | |
| | | |||||
| * | docs(zkvms/zkm): Add detailed documentation comments | 2025-02-10 | -0/+33 | 1cb8861 | |
| | | |||||
| * | fix(zkvms/sp1): When benchmarking verification, only benchmark the function call | 2025-02-10 | -3/+5 | 10fb533 | |
| | | |||||
| * | fix(zkvms/sp1): Remove unused guests_macro symlink | 2025-02-10 | -1/+0 | f6f4aa5 | |
| | | |||||
| * | docs(zkvms/sp1): Add detailed documentation comments | 2025-02-10 | -0/+30 | cff7490 | |
| | | |||||
