RISC Zero is a zero-knowledge verifiable general computing platform based on zk-STARKs and the RISC-V microarchitecture.
Full Changelog: https://github.com/risc0/risc0/compare/v0.19.0...v0.19.1
Full Changelog: https://github.com/risc0/risc0/compare/v0.19.0...v0.19.1-rc.1
docs directory by @pdg744 in https://github.com/risc0/risc0/pull/881
Full Changelog: https://github.com/risc0/risc0/compare/v0.18.0...v0.19.0
Full Changelog: https://github.com/risc0/risc0/compare/v0.19.0-rc.3...v0.19.0-rc.4
Full Changelog: https://github.com/risc0/risc0/compare/v0.19.0-rc.2...v0.19.0-rc.3
Full Changelog: https://github.com/risc0/risc0/compare/v0.19.0-rc.1...v0.19.0-rc.2
Full Changelog: https://github.com/risc0/risc0/compare/v0.19.0-alpha.1...v0.19.0-rc.1
docs directory by @pdg744 in https://github.com/risc0/risc0/pull/881
Full Changelog: https://github.com/risc0/risc0/compare/v0.18.0...v0.19.0-alpha.1
Our 0.18 release upgrades the Bonsai SDK with Groth16 SNARK seals for better on-chain verification, better error handling, and more. In the zkVM, this release separates host and guest build toolchains and also supports reproducibly building the same ImageID for the same zkVM code by using a consistent Docker environment.
Thank you to community members @austinabell and @winor30 for their contributions to this release!
rustc for host and guest code. This has allowed us to move the default host toolchain to the stable channel. The guest toolchain remains on a nightly release of 1.69.cargo risczero build command to build zkVM guest programs using a Docker container, which enables ImageIDs to remain consistent across builds. See #799 for details.upload_img and upload_img_file no longer return ImageIdExists errors. Instead they return a boolean, true if the image exists on the server.post_state_digest for easy on-chain verification.SystemState root in the ReceiptMetadata was not guaranteed to be a hiding commitment.host::api::Connector to users by @tzerrell in https://github.com/risc0/risc0/pull/864
factors-->hello-world; moving tutorial out of readme by @pdg744 in https://github.com/risc0/risc0/pull/765
--po2 flag to loop.rs by @mothran in https://github.com/risc0/risc0/pull/858
Full Changelog: https://github.com/risc0/risc0/compare/v0.17.0...v0.18.0
With our 0.17 release, we have expanded our Bonsai content and updated the installation process. The latter change means existing users will have to install again when upgrading, by running cargo install cargo-risczero and cargo risczero install. See the Getting Started section of our README for prerequisites and more details. We've also added a developer mode for more rapid development and continued to streamline the proof and receipt APIs, among other changes.
Thank you to community members @criadoperez, @austinabell, and @roseiliend for their contributions to this release!
cargo risczero install tool for setting up the RISC Zero toolchain. Fixes in this release require a "risc0" rustup toolchain; the cargo risczero install command will install this toolchain and do other RISC Zero setup. All users, new and old, will need to run this command to install the RISC Zero zkVM. Full details are available in the Getting Started section of our README.RISC0_DEV_MODE environment variable controls whether developer mode is enabled, and this feature can be fully disabled at build time, regardless of environment, by using the disable-dev-mode feature flag on the risc0-zkvm crate.let receipt = default_prover().prove_elf(env, SOME_ELF).unwrap();. Receipt implementation details are encapsulated in an InnerReceipt object which most users will not need to interact with. The Prover now has additional high level methods, included prove and prove_elf. See the Executor, Receipt, and Prover sections of our docs for the current API, and this PR for details about the changes.risc0-binfmt crate. See its docs for details.cc crate to a specific version as a workaround to build problems when using its latest version.