Skip to content
/ jolt Public

The simplest and most extensible zkVM. Fast and fully open source from a16z crypto and friends. ⚡

License

Notifications You must be signed in to change notification settings

a16z/jolt

Folders and files

NameName
Last commit message
Last commit date
Feb 6, 2025
Dec 18, 2024
Feb 20, 2025
Feb 6, 2025
Apr 9, 2024
Feb 22, 2025
Feb 22, 2025
Jan 7, 2025
Feb 11, 2025
Feb 22, 2025
Mar 14, 2024
Oct 24, 2024
Jun 20, 2024
Feb 22, 2025
Jan 7, 2025
Dec 16, 2019
Feb 21, 2025
Mar 14, 2024
Aug 9, 2024
Nov 22, 2024
Dec 4, 2023

Repository files navigation

Jolt

imgs/jolt_alpha.png

Just One Lookup Table.

Jolt is a zkVM (zero-knowledge virtual machine) for RISC-V, built to be the simplest, fastest, and most extensible general-purpose of its kind. This repository currently contains an implementation of Jolt for the RISC-V 32-bit Base Integer instruction set (RV32I). Contributors are welcome!

The Jolt paper was written by Arasu Arun, Srinath Setty, and Justin Thaler.

Resources

Quickstart

Note

Jolt is in alpha and is not suitable for production use at this time.

For developers looking to build using Jolt, check out the Quickstart guide.

For developers looking to contribute to Jolt, follow the instructions below.

Installation

You will need Rust nightly.

If you have rustup installed, you do not need to do anything as it will automatically install the correct toolchain and any additional targets on the first cargo invocation.

Clone this repo:

git clone git@github.com:a16z/jolt.git

To check if rustup has picked the right version of Rust run rustup show inside the cloned repository.

cd jolt; rustup show.

Build

This repository uses workspaces, and each workspace can be built individually, e.g.

cargo build -p jolt-core

For faster incremental builds, use the build-fast profile:

cargo build --profile build-fast -p jolt-core

Test

Unit and end-to-end tests for jolt-core can be run using the following command:

cargo test -p jolt-core

Examples in the examples directory can be run using e.g.

cargo run --release -p sha2-chain

CUDA Support

JOLT supports CUDA acceleration via icicle.

Dependencies:

  1. Install CUDA Toolkit
  2. Install CMake

Now you may build Jolt with CUDA acceleration using the --features icicle flag.

Build

cargo build -p jolt-core --features icicle

Bench

# Set the icicle backend path - this won't be needed in the future
export ICICLE_BACKEND_INSTALL_DIR=$(pwd)/target/debug/deps/icicle/lib/backend
cargo bench --bench msm_batch --no-fail-fast -p jolt-core --features icicle

Note - NVIDIA doesn't support cross compilation on MacOS. Only Windows or Linux.

Performance profiling

Jolt uses tracing_chrome for performance profiling.

To generate a trace, run:

cargo run --release -p jolt-core trace --name sha3 --format chrome --pcs hyper-kzg

Where --name can be sha2, sha3, sha2-chain, or fibonacci. The corresponding guest programs can be found in the examples directory. The benchmark inputs are provided in bench.rs.

The above command will output a JSON file, e.g. trace-1712455107389520.json, which can be viewed in Perfetto.

CI Benchmarking

We have enabled benchmarking during CI to track performance changes over time in terms of prover runtime and peak memory usage.

Acknowledgements

This repository started as a fork of https://github.com/arkworks-rs/spartan. Original Spartan code by Srinath Setty.

Disclaimer

This code is being provided as is. No guarantee, representation or warranty is being made, express or implied, as to the safety or correctness of the code. It has not been audited and as such there can be no assurance it will work as intended, and users may experience delays, failures, errors, omissions or loss of transmitted information. Nothing in this repo should be construed as investment advice or legal advice for any particular facts or circumstances and is not meant to replace competent counsel. It is strongly advised for you to contact a reputable attorney in your jurisdiction for any questions or concerns with respect thereto. a16z is not liable for any use of the foregoing, and users should proceed with caution and use at their own risk. See a16z.com/disclosures for more info.