RISC Zero
- Name: RISC Zero
- URL: https://risczero.com/
- Category: Zero-knowledge proving infrastructure / zkVM / verifiable-computation platform
- Tags: ethereum-ecosystem
- Summary: RISC Zero is a major zkVM stack, not just a proof library. What matters is the full runtime-and-verifier line: the zkVM, receipts, Ethereum verifier path, and the proving services that grew around it. That product cut is still useful, but the adjacent implementation and migration boundary now also lives in risc-zero, which is the cleaner place to reason about toolchain stewardship, docs authority, and the Bonsai-to-Boundless shift in production proving defaults.
- What it does:
- Provides a zero-knowledge virtual machine that proves correct execution of arbitrary Rust code, with broader RISC-V-targetable language support surfaced through the underlying architecture
- Gives developers a toolchain for compiling guest code, generating proofs, producing receipts, and verifying public outputs against an ImageID / expected binary
- Supports blockchain integration through onchain verifier contracts and related Ethereum-facing documentation
- Offers both local/self-managed proving paths and a production remote-proving surface through Boundless
- Publishes detailed technical and security material including a proof-system PDF, security-model docs, audits, and an extensive open-source repository
- Key claims:
- Homepage positions RISC Zero as infrastructure for verifiable computation where users can be cryptographically certain outputs are correct and verify them far faster than recomputing everything themselves
- zkVM docs say developers can prove correct execution of arbitrary Rust code and build zero-knowledge applications using existing Rust packages
- Security-model docs describe an end-to-end stack that includes the zkVM, prover layers, STARK-to-SNARK compression, and onchain verifier contracts on Ethereum networks
- Official docs explicitly warn that critical privacy users should exercise caution and independently validate application-level security, which is a useful primary-source trust signal
- Boundless materials show RISC Zero’s surface extending into production prover-network infrastructure rather than stopping at an SDK or research repo
- Whitepaper: An official technical proof-system PDF was found and saved locally as
../whitepapers/risc-zero-proof-system-in-detail.pdf; see../whitepapers/risc-zero-primary-sources-2026-04-25.mdfor the broader primary-source snapshot. - Sources:
Internal linkages
- Company/operator boundary for toolchain stewardship and proving-path migration: risc-zero.
- Historical centralized proving surface: bonsai.
- Decentralized prover-market layer: boundless.
- Closest broad proving-stack peer: succinct.
Protocol / company boundary
- Keep this note at the project layer: the zkVM architecture, receipts, verifier path, and the broad verifiable-compute stack are still the important product / protocol surface.
- risc-zero is the cleaner entity note for implementation stewardship, remote-proving guidance, the old Bonsai service boundary, and the docs / toolchain defaults developers inherit.
- bonsai and boundless remain useful child notes because they capture materially different remote-proving control surfaces rather than just documentation reshuffles.
Control surface
-
At the project layer, the important mechanism is how developers compile guest code, generate proofs, verify receipts, and connect those proofs to onchain or offchain applications.
-
For questions about who steers the toolchain, publishes the canonical docs, retires one proving service in favor of another, or defines the default remote-proving path, read risc-zero.
-
Read RISC Zero as the verifiable-compute stack; read the company note when the live question is about operational stewardship of that stack.
-
Last reviewed: 2026-08-09 UTC