Transaction Approval / User Controls ZIP #91
Conversation
✅ Deploy Preview for zcash-zips-qedit ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
AntoineRondelet
force-pushed
the
zip-approval
branch
3 times, most recently
from
e702a44 to
9343183
Compare
AntoineRondelet
changed the title
AntoineRondelet
force-pushed
the
zip-approval
branch
from
9343183 to
aae09b0
Compare
AntoineRondelet
force-pushed
the
zip-approval
branch
2 times, most recently
from
7112a88 to
f5b53e1
Compare
vivek-arte
left a comment
vivek-arte
left a comment
There was a problem hiding this comment.
Added some math notation suggestions. Also, would need some updates to make the ZIP build on top of ZIP 226/227 and TxV6 (ZIP 230) instead of directly on top of NU5 (Vanilla Orchard)
zips/draft-approval.rst
Outdated
|
|
||
| Given the Orchard address of the recipient of the output note of an Orchard Action (in the form: $d | pk_d$, see [#protocol-raw-address]_), and given that $g_d$ is a Pallas curve point, derived from $d$ (see [#protocol-diversify-hash]_) - the approval signature derivation goes as follows: | ||
|
|
||
| 1. The sender sends the $OrchardActionDescription$ (the preimage of the message to be signed, as per [#protocol-actions]_) for the recipient to sign. |
There was a problem hiding this comment.
Use OrchardZSA terminology - can also add a [#zip-230]_ reference, that is where the encoding of OrchardZSAAction is defined.
| 1. The sender sends the $OrchardActionDescription$ (the preimage of the message to be signed, as per [#protocol-actions]_) for the recipient to sign. | |
| 1. The sender sends the OrchardZSA Action Description, ``OrchardZSAAction`` (the preimage of the message to be signed, as per [#protocol-actions]_), for the recipient to sign. |
There was a problem hiding this comment.
Is the detail in parentheses necessary?
There was a problem hiding this comment.
Not a must, but I don't think it is an issue to keep either. Happy to remove if you're opinionated about that :)
zips/draft-approval.rst
Outdated
| In fact, such proof of knowledge of $ivk$ can be obtained by using a Schnorr Signature on the Action (the message) with $ivk$ as signing/secret key and $g_d$ as group generator. | ||
|
|
||
| **Note:** Zcash Orchard already uses a Schnorr-based signature scheme instantiated with the Pallas curve (see RedPallas [#protocol-redpallas]_). | ||
| As of NU6, RedPallas is used to instantiate $SpendAuthSig^{Orchard}$ and $BindingSig^{Orchard}$. |
There was a problem hiding this comment.
This was added simply to note that Schnorr signatures are already used in Zcash, so we're not adding brand new primitives to the protocol. Happy to remove tbh, I'm not really opinionated about this :)
There was a problem hiding this comment.
Ah, understood. We can leave it in then.
vivek-arte
left a comment
vivek-arte
left a comment
There was a problem hiding this comment.
Just spotted a few LaTeX improvements
Co-authored-by: Vivek Arte <46618816+vivek-arte@users.noreply.github.com>
3 participants
This PR introduces the TX approval / user controls ZIP.
Motivation
In the current version of Zcash, fund transfers occur without the explicit consent of recipients. While this simplicity offers convenience, it creates significant challenges for users of the network (e.g. individuals or businesses). The goal of this ZIP is to design a mechanism where the recipient of shielded funds on Zcash (for any type of ZSA) can confirm (or ‘approve’) the receipt of the funds on chain. The proposed controls offer robust safeguarding solutions while maintaining Zcash’s core privacy features.
ZIP preview:
https://deploy-preview-91--zcash-zips-qedit.netlify.app/draft-approval
Blog post:
https://forum.zcashcommunity.com/t/introducing-transaction-controls-in-zcash/49640
Full writeup:
https://hackmd.io/@47RQMp3nR22v0fGRiy03DQ/rkLWGBVaR
Upstream PR:
zcash#980