Section IV
Jolt Pro GR
Zero-Knowledge Execution Engine
Jolt Pro GR proves every transaction correct over native 64-bit arithmetic, with no trusted setup and no ceremony, targeting 128-bit security with machine-checked core primitives.
what it does
What Jolt Pro GR Does
A validator confirms an entire block by checking one proof. It never re-runs a transaction. It never even needs to see most of them.
That is the trade the whole architecture rests on: doing the work is expensive, checking that it was done is cheap. Every chain that re-executes has quietly agreed to pay the expensive price on every machine, forever, and then wondered aloud why it could not scale.
Are you sure you need to re-execute everything?
performance
Performance Advantages
Prime-field proof systems carry a hidden tax. A RISC-V program works on 64-bit words. A prime field does not have 64-bit words. So every ordinary operation — an add, a shift, a comparison — gets emulated inside an arithmetic that was never meant to hold it, and the witness inflates on every instruction.
Jolt Pro GR works over a Galois ring built on 64-bit arithmetic, so a 64-bit word is a 64-bit word. The emulation layer does not get optimized. It stops existing.
This is a constant factor, not an asymptotic one. Constant factors are what you actually pay for.
no trusted setup
No Trusted Setup
A trusted setup is a ceremony where a group of strangers generate a secret and promise to destroy it. If any single one of them kept a copy, they can forge proofs forever, and from the outside there is no way to tell.
The industry solved this socially: more participants, more cameras, more ceremony. It is a thoughtful mitigation of a problem that should not exist.
There is no ceremony here to attend. The commitments are hash-based and transparent from the first block. There is no secret to keep, so there is nothing anyone could have kept.
risc v
Write in Any Language
Write your contract in Rust. Or C. Or anything that compiles to RISC-V.
No new language to learn, no bespoke VM semantics, no standard library rewritten from scratch by six people. Proof generation happens underneath and you do not write a line of cryptography.
The reason most chains ship a custom language is that their proof system could not handle a real instruction set. That is a limitation of the prover leaking upward into the developer's job, and developers have been paying for it ever since.