| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| | |
|
| | |
|
| |
|
|
| |
makes a difference
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Now, you have zkvm/guest_implementation packages, where you'll build and
run the zkVM with guest_implementation
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
For example, in `Vec<...>`, `<` is Joint and before it would get
skipped.
|
| |
|
|
| |
from TOML file
|
| |
|
|
| |
Use it in multiple zkVMs, simplifying codebase
|
| | |
|
| |
|
|
| |
For use in Nexus
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
to items
|
| |
|
|
|
|
| |
Had to reimplement and modify the build macro function so it would take
an elf path, instead of always doing a manual build.
Additionally, had to hard-code a **lot** of values.
|
| |
|
|
| |
It expects certain custom funcitonality from guest
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|