Expand description
§sapling
§Nomenclature
All types in the sapling-crypto
crate, unless otherwise specified, are
Sapling-specific types. For example, PaymentAddress
is documented as being a
shielded payment address; we implicitly mean it is an Sapling payment address (as
opposed to e.g. an Orchard payment address, which is also shielded).
§Feature flags
multicore
(enabled by default) — Enables multithreading support for creating proofs.test-dependencies
— Exposes APIs that are useful for testing, such asproptest
strategies.
Re-exports§
pub use bundle::Bundle;
pub use keys::Diversifier;
pub use keys::NullifierDerivingKey;
pub use keys::ProofGenerationKey;
pub use keys::SaplingIvk;
pub use keys::ViewingKey;
pub use note::Note;
pub use note::Rseed;
Modules§
- Types and functions for building Sapling transaction components.
- The Sapling circuits.
- Various constants used by the Sapling protocol.
- Implementation of group hashing into Jubjub.
- Sapling key components.
- Implementation of in-band secret distribution for Zcash transactions.
- Implementation of the Pedersen hash function used in Sapling.
- Abstractions over the proving system and parameters.
- testing
test-dependencies
- Monetary values within the Sapling shielded pool.
- Sapling key derivation according to ZIP 32 and ZIP 316
Structs§
- The root of a Sapling commitment tree.
- Batch validation context for Sapling.
- A node within the Sapling commitment tree.
- Typesafe wrapper for nullifier values.
- A Sapling payment address.
- A context object for verifying the Sapling components of a single Zcash transaction.
Constants§
Functions§
- Compute a parent node in the Sapling commitment tree given its two children.