| Commit message (Collapse) | Author | Age | Lines | SHA |
|---|
| | |
|
| |
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
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
|
| |
|
|
| |
versions
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
during the process
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Use it in multiple zkVMs, simplifying codebase
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|
|
Currently only setup for proving
|
