From 6e42aaeed60a4a82ddc6670b3ee4681165d64820 Mon Sep 17 00:00:00 2001 From: Greg Pfeil Date: Wed, 29 Mar 2023 12:49:05 -0600 Subject: [PATCH] Update release-notes for transparent change restriction Co-authored-by: Kris Nuttycombe --- doc/release-notes.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/doc/release-notes.md b/doc/release-notes.md index 0ed0ba42f..79b7796b7 100644 --- a/doc/release-notes.md +++ b/doc/release-notes.md @@ -25,9 +25,10 @@ RPC Changes while you should already be checking the async operation status, there are now more cases that may trigger failure at that stage. - The `AllowRevealedRecipients` privacy policy is now required in order to choose a - transparent change address for a transaction (and thus `AllowFullyTransparent` - is required for the transaction, since transparent change implies a - transparent sender). + transparent change address for a transaction. This will only occur when the wallet + is unable to construct the transaction without selecting funds from the transparent + pool, so the impact of this change is that for such transactions, the user must specify + `AllowFullyTransparent`. [Deprecations](https://zcash.github.io/zcash/user/deprecation.html) --------------