Skip to content

zcash_primitives-0.21.0

@nuttycom nuttycom tagged this 17 Dec 14:39
[0.21.0] - 2024-12-16
=====================

Added
-----
- `zcash_primitives::legacy::Script::address`
- `zcash_primitives::transaction`
  - `TransactionData::try_map_bundles`
  - `builder::{PcztResult, PcztParts}`
  - `builder::Builder::build_for_pczt`
  - `components::transparent`:
    - `pczt` module.
    - `EffectsOnly`
    - `impl MapAuth<Authorized, Authorized> for ()`
    - `builder::TransparentSigningSet`
  - `sighash::SighashType`

Changed
-------
- Migrated to `sapling-crypto` version `0.4`.
- `zcash_primitives::transaction::components::transparent`:
  - `builder::TransparentBuilder::add_input` now takes `secp256k1::PublicKey`
    instead of `secp256k1::SecretKey`.
  - `Bundle<Unauthorized>::apply_signatures` has had its arguments replaced with
    a function providing the sighash calculation, and `&TransparentSigningSet`.
  - `builder::Error` has a new variant `MissingSigningKey`.
- `zcash_primitives::transaction::builder`:
  - `Builder::add_orchard_spend` now takes `orchard::keys::FullViewingKey`
    instead of `&orchard::keys::SpendingKey`.
  - `Builder::add_sapling_spend` now takes `sapling::keys::FullViewingKey`
    instead of `&sapling::zip32::ExtendedSpendingKey`.
  - `Builder::add_transparent_input` now takes `secp256k1::PublicKey` instead of
    `secp256k1::SecretKey`.
  - `Builder::build` now takes several additional arguments:
    - `&TransparentSigningSet`
    - `&[sapling::zip32::ExtendedSpendingKey]`
    - `&[orchard::keys::SpendAuthorizingKey]`
- `zcash_primitives::transaction::sighash`:
  - `SignableInput::Transparent` is now a wrapper around
    `zcash_transparent::sighash::SignableInput`.
Assets 2
Loading