Open adityapk00 opened 3 years ago
CC: @nuttycom
CompactNotes do not contain outCiphertext
(we trimmed out absolutely everything we could to make trial-decryption bandwidth as minimal as possible), so this can't be done without making those notes less compact. We could maybe add a flag that allows light clients to request that these be added, but it would be distinguishable to network observers.
This is a mild bummer.
I think it would be a good idea to add it to LightwalletD as an optional
, and have light clients be able to request it in GetBlock
or GetBlockRange
. This will significantly improve sync speed.
out_ciphertext
is like 80 bytes, right? Not insignificant, but not that big either, so I think it would still be a good idea to do it.
@LarryRuane @gmale
See also: LightwalletD support for a nullifier spent check RPC (https://github.com/zcash/lightwalletd/issues/352)
The
zcash_primitives
create currently has atry_sapling_output_recovery
method that allows wallets to recover outgoing transactions sent by the wallet using anovk
. This allows wallets to show outgoing transactions and memos to the user. This method works on the full sapling note.It would be nice to also have
try_sapling_compact_note_output_recovery
that works on the Compact Note. It would be the equivalent oftry_sapling_compact_note_decryption
, but using anovk
instead of anivk
.The method could be (where the
Output
is aCompactOutput
):