#zcash #sapling #crypto #blockchain #cryptocurrency


A library for loading Zcash Sapling parameters

2 unstable releases

0.2.0 Mar 31, 2020
0.1.0 Mar 31, 2020

#11 in #sapling

Download history 3422/week @ 2024-02-05 2154/week @ 2024-02-12 2245/week @ 2024-02-19 2958/week @ 2024-02-26 4567/week @ 2024-03-04 1796/week @ 2024-03-11 1457/week @ 2024-03-18 1225/week @ 2024-03-25 806/week @ 2024-04-01 1411/week @ 2024-04-08 2583/week @ 2024-04-15 1807/week @ 2024-04-22 2788/week @ 2024-04-29 2823/week @ 2024-05-06 2198/week @ 2024-05-13 1359/week @ 2024-05-20

9,242 downloads per month
Used in 10 crates (5 directly)


112 lines


Crates.io Authors License

This library imports Zcash Sapling parameters natively into your Rust code.


Use this library in your Rust code, add the following to your Cargo.toml:

wagyu-zcash-parameters = { version = "0.2.0" }

In your Rust code, add the following:

use wagyu_zcash_parameters::load_sapling_parameters;

// Loads Zcash Sapling parameters as buffers
let (spend, output) = load_sapling_parameters();

println!("Number of bytes in Sapling spend parameter: {:?}", spend.len());
println!("Number of bytes in Sapling output parameter: {:?}", output.len());


This crate dynamically produces the Zcash Sapling parameters by fetching and recombining the raw parameter data from a collection of crates published specifically for constructing the Zcash Sapling parameters.

Crates.io maintains a maximum size limit of 10,485,760 bytes for each published crate. This size restriction is beyond the capacity of the Zcash Sapling spend and output parameters, which are 47,958,396 bytes and 3,592,860 bytes respectively.


To run the test, run:

cargo test

To run the example, run:

cargo run --example load_sapling_parameters

The example should output:

Number of bytes in Sapling spend parameter: 47958396
Number of bytes in Sapling output parameter: 3592860


This work is licensed under either of the following licenses, at your discretion.

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.