You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This responds to zcash_client_backend (backed by zcash_client_sqlite) not handling transparent change. When querying the AccountBalance of a particular account, the unshielded balance will return a Balance struct where the change_pending_confirmation field will always be NonNegativeAmount::ZERO.
Currently, zcash_client_backend assumes that ephemeral transparent addresses should only contain funds that will be spent on a subsequent transaction (e.g.: when sending funds from the shielded pool to a TEX Address).
originated by #1411
function
add_transparent_account_balances
does not distinguish between change and non-change pending funds.librustzcash/zcash_client_sqlite/src/wallet/transparent.rs
Lines 382 to 389 in bf8b39a
This responds to
zcash_client_backend
(backed by zcash_client_sqlite) not handling transparent change. When querying theAccountBalance
of a particular account, theunshielded
balance will return aBalance
struct where thechange_pending_confirmation
field will always beNonNegativeAmount::ZERO
.Currently,
zcash_client_backend
assumes that ephemeral transparent addresses should only contain funds that will be spent on a subsequent transaction (e.g.: when sending funds from the shielded pool to a TEX Address).librustzcash/zcash_client_backend/src/data_api/wallet.rs
Lines 1208 to 1223 in bf8b39a
In order to enabling spending transparent funds beyond sending to TEX addresses, this assumption shouldn't be made anymore.
Related: #1360 #1370
The text was updated successfully, but these errors were encountered: