This addresses #3 of upstream issue
https://github.com/zcash/zcash/issues/3996 .
Any software that creates a transaction outside of the RPC interface
MUST check if synced==true beforehand, otherwise metadata leakage which
leads to linkability analysis is possible.
The z_sendmany, z_shieldcoinbase and z_mergetoaddress RPCs have their
own synced checks, so it's not needed to look at this new synced value
when using those RPCs.
This addresses upstream issue https://github.com/zcash/zcash/issues/3996
by preventing z_sendmany, z_mergecoinbase and z_shieldcoinbase from
making shielded transactions if the node is out of sync. This prevents
metadata leakage which can be used in blockchain analysis.
This addresses #3 of upstream issue
https://github.com/zcash/zcash/issues/3996 .
Any software that creates a transaction outside of the RPC interface
MUST check if synced==true beforehand, otherwise metadata leakage which
leads to linkability analysis is possible.
The z_sendmany, z_shieldcoinbase and z_mergetoaddress RPCs have their
own synced checks, so it's not needed to look at this new synced value
when using those RPCs.
This addresses upstream issue https://github.com/zcash/zcash/issues/3996
by preventing z_sendmany, z_mergecoinbase and z_shieldcoinbase from
making shielded transactions if the node is out of sync. This prevents
metadata leakage which can be used in blockchain analysis.
