Update release-notes for transparent change restriction
Co-authored-by: Kris Nuttycombe <kris@nutty.land>
This commit is contained in:
parent
1786c60677
commit
6e42aaeed6
|
@ -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)
|
||||
--------------
|
||||
|
|
Loading…
Reference in New Issue