| 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.
|
| | |
|
| | |
|
| |
|
|
|
| |
In certain cases, we would get errors that the "x" type cannot be
inferred.
|
| | |
|
| | |
|
| |
|
|
| |
This follows the same change which was made in mcl-blockchain
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
So you can make code modifications compile-time, based on the zkVM
|
| |
|
|
|
|
|
|
| |
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
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
to host
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
type composition
|
| |
|
|
| |
Also handles multidimentional vec
|
| | |
|
| |
|
|
| |
and use default environments
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
