From d8885bec55edf85f4a96897e5ce2038c3b2bcd9d Mon Sep 17 00:00:00 2001 From: Kris Nuttycombe Date: Thu, 9 Mar 2023 17:29:58 -0700 Subject: [PATCH] Update Sapling note encryption for `zcash_note_encryption 0.3.0` Fixes zcash/librustzcash#455 Extracted from: https://github.com/zcash/librustzcash/commit/d6fafa291bca1a7d5154d08bcf75f5d664b0018a --- src/lib.rs | 9 --------- 1 file changed, 9 deletions(-) diff --git a/src/lib.rs b/src/lib.rs index fb01b0d..49c2179 100644 --- a/src/lib.rs +++ b/src/lib.rs @@ -171,15 +171,6 @@ pub trait Domain { fn kdf(secret: Self::SharedSecret, ephemeral_key: &EphemeralKeyBytes) -> Self::SymmetricKey; /// Encodes the given `Note` and `Memo` as a note plaintext. - /// - /// # Future breaking changes - /// - /// The `recipient` argument is present as a secondary way to obtain the diversifier; - /// this is due to a historical quirk of how the Sapling `Note` struct was implemented - /// in the `zcash_primitives` crate. `recipient` will be removed from this method in a - /// future crate release, once [`zcash_primitives` has been refactored]. - /// - /// [`zcash_primitives` has been refactored]: https://github.com/zcash/librustzcash/issues/454 fn note_plaintext_bytes(note: &Self::Note, memo: &Self::Memo) -> NotePlaintextBytes; /// Derives the [`OutgoingCipherKey`] for an encrypted note, given the note-specific