8 stable releases (3 major)
|4.0.0||Feb 2, 2021|
|3.0.1||Feb 2, 2021|
|3.0.0||Jan 28, 2021|
|2.0.0||Jan 18, 2020|
#145 in Cryptography
36,885 downloads per month
Used in 14 crates (4 directly)
Contains (Zip file, 280KB) aggregated-range-proof.sketch
The fastest Bulletproofs implementation ever, featuring single and aggregated range proofs, strongly-typed multiparty computation, and a programmable constraint system API for proving arbitrary statements (under development).
This library implements Bulletproofs using Ristretto,
ristretto255 implementation in
curve25519-dalek. When using the parallel
formulas in the
curve25519-dalek AVX2 backend, it
can verify 64-bit rangeproofs approximately twice as fast as the
libsecp256k1-based Bulletproofs implementation.
This library provides implementations of:
Single-party proofs of single or multiple ranges, using the aggregated rangeproof construction;
Online multi-party computation for rangeproof aggregation between multiple parties, using session types to statically enforce correct protocol flow;
A programmable constraint system API for expressing rank-1 constraint systems, and proving and verifying proofs of arbitrary statements (unstable, under development with the
Online multi-party computation for aggregated constraint system proofs (planned future work).
These proofs are implemented using Merlin transcripts, allowing them to be arbitrarily composed with other proofs without implementation changes.
The constraint system API is provided FOR EXPERIMENTS ONLY, and must be
enabled by specifying the
yoloproofs feature. It is not covered by semver
compatibility and is SUBJECT TO CHANGE WITHOUT NOTICE.
yoloproofs feature is disabled in the published version of the
crate, so it can only be used by specifying a git dependency on the
branch. This means that it is not possible to publish a crate using the R1CS
API, because it is FOR EXPERIMENTS ONLY.
The user-facing documentation for this functionality can be found here. In addition, the library also contains extensive notes on how Bulletproofs work. These notes can be found in the library's internal documentation:
- how Bulletproofs work;
- how the range proof protocol works;
- how the inner product proof protocol works;
- how the aggregation protocol works;
- how the Bulletproof constraint system proofs work (under development);
- how the constraint system reduction works (under development);
- how the aggregated constraint system proofs work (future work).
The following table gives comparative timings for proving and verification of a 64-bit rangeproof on an Intel Skylake-X i7-7800X (@3.5GHz, Turbo Boost disabled). Times are in microseconds (lower is better), with the relative speed compared to the fastest implementation.
|Implementation||Group||Proving (μs)||rel||Verification (μs)||rel|
Use of the
curve25519-dalek IFMA backend gives another 1.5x speedup on a
Cannonlake i3-8121U, increasing the verification speedup 3x over libsecp
and 7x over Monero, but these processors are not yet generally available.
This crate also contains other benchmarks; see the Tests and Benchmarks section below for details on how to run them all.
The following example shows how to create and verify a 32-bit rangeproof.
# # # # # // Generators for Pedersen commitments. These can be selected // independently of the Bulletproofs generators. let pc_gens = PedersenGens::default(); // Generators for Bulletproofs, valid for proofs up to bitsize 64 // and aggregation size up to 1. let bp_gens = BulletproofGens::new(64, 1); // A secret value we want to prove lies in the range [0, 2^32) let secret_value = 1037578891u64; // The API takes a blinding factor for the commitment. let blinding = Scalar::random(&mut thread_rng()); // The proof can be chained to an existing transcript. // Here we create a transcript with a doctest domain separator. let mut prover_transcript = Transcript::new(b"doctest example"); // Create a 32-bit rangeproof. let (proof, committed_value) = RangeProof::prove_single( &bp_gens, &pc_gens, &mut prover_transcript, secret_value, &blinding, 32, ).expect("A real program could handle errors"); // Verification requires a transcript with identical initial state: let mut verifier_transcript = Transcript::new(b"doctest example"); assert!( proof .verify_single(&bp_gens, &pc_gens, &mut verifier_transcript, &committed_value, 32) .is_ok() );
To compile successfully, you will need to have nightly Rust installed, rather than stable.
You can install nightly Rust with rustup:
rustup default nightly
Tests and Benchmarks
Run tests with
cargo test. Run benchmarks with
cargo bench. This crate
uses criterion.rs for benchmarks.
yoloproofs feature enables support for rank-1 constraint system proofs.
It is UNSTABLE AND UNSUITABLE FOR DEPLOYMENT, and PROVIDED FOR TESTING
avx2_backend feature enables
curve25519-dalek's AVX2 backend,
which implements curve arithmetic using parallel
formulas. To use it for Bulletproofs, the
target_cpu must support AVX2:
RUSTFLAGS="-C target_cpu=skylake" cargo bench --features "avx2_backend"
Skylake-X CPUs have double the AVX2 registers. To use them, try
RUSTFLAGS="-C target_cpu=skylake-avx512" cargo bench --features "avx2_backend"
This prevents spills in the AVX2 parallel field multiplication code, but causes worse code generation elsewhere ¯\_(ツ)_/¯
This is a research project sponsored by Interstellar, developed by Henry de Valence, Cathie Yun, and Oleg Andreev.