-
Notifications
You must be signed in to change notification settings - Fork 106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sapling/Orchard note encryption implementation. #269
Comments
@dconnolly does this belong in the "Wallet Support" milestone, or the "Transaction Validation" milestone? |
Wallet support, otherwise we can't send money properly |
Splitting the decryption part that we need for ZIP-212 into #3002 |
We're not planning to do full-node wallet work any time soon. If we do, we'll need to decide if this ticket is in scope, and update its content, because the spec has changed since it was created. |
Ashbury suggests we should make our terms more explicit and verbose.
We need an implementation of note encryption/decryption. This has possible overlap with librustzcash.
Two levels of completion:
All the types to represent in the transaction
Some types:
sapling::Note (plaintext)
sapling::OutCiphertext
sapling::EncryptedCiphertext
And implementing methods to do the note encryption
NoteEncryptionBuilder
But first:
note commitment trees: #36
addresses
as above, full Note implementation
Related: #181
Spec references:
https://zips.z.cash/protocol/protocol.pdf#saplingsend
https://zips.z.cash/protocol/protocol.pdf#orchardsend
https://zips.z.cash/protocol/protocol.pdf#saplingandorchardencrypt
Note that ZIP-212 is included in this ticket (it was incorporated into the spec)
The text was updated successfully, but these errors were encountered: