Jolt’s Privacy Patch Changes What “zkVM” Should Mean

A new Jolt upgrade makes a useful distinction in the zkVM market: a short proof is not automatically a private proof.

In a March 3, 2026 technical post, the Jolt team announced that its open-source RISC-V zkVM now supports zero knowledge through a technique called NovaBlindFold. The change targets a weakness in Jolt’s original design: messages produced by its sum-check prover could reveal information about the witness, or the private input used to execute a program.

The new design blinds those messages with hiding commitments. A second proof then demonstrates that the committed values would have passed the verifier’s checks. Jolt describes the result as a transparent zero-knowledge proof that does not require SNARK recursion, a trusted setup, or a separate wrapping system.

The reported engineering trade-off is unusually narrow. According to the project’s announcement, the privacy layer adds roughly 3 KB to the proof and causes essentially no increase in prover time. That does not mean every workload will receive identical results: the figure is a project-reported outcome, not an independent benchmark across hardware and programs.

Why this matters for builders

The terminology correction is more important than the headline number. Many systems described as “zkVMs” primarily provide succinctness: a verifier can check a computation without replaying it. Zero knowledge adds a different property: the proof should not reveal the private inputs or intermediate witness beyond what the claimed output implies.

Jolt’s architecture attempts to provide both properties in one transparent system. That could make the same execution framework useful for public verifiable computation and privacy-sensitive applications such as private credentials, confidential data processing, or proofs generated on constrained devices.

The repository also gives developers a practical starting point: Jolt targets RV64IMAC, is written as an open-source Rust project, and includes a quickstart path and profiling tools. But the project is not production-ready. Jolt’s official repository explicitly labels it alpha and says it is not suitable for production use at this time.

The cautious takeaway is that Jolt’s update is not proof that private zkVMs have become solved infrastructure. It is a concrete architectural move toward separating, then combining, succinctness and privacy without hiding the system behind recursive proof machinery. For developers evaluating a zkVM, “Can it prove execution?” and “Does it keep the witness private?” should now be treated as separate checklist items.