zec
/
zips
mirror of https://github.com/zcash/zips.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Update zip-0312.rst

This commit is contained in:
Deirdre Connolly 2023-02-07 12:30:05 -05:00 committed by GitHub
parent 8836e22610
commit 9512ead14c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
zip-0312.rst
View File

@ -219,12 +219,12 @@ from regular FROST which just requires an authenticated channel.)
In Zcash, the message that needs to be signed is actually the SIGHASH
transaction hash, which does not convey enough information for the signers to
decide if they want to authorize the transaction or not. Therefore, in practice,
more data is needed to be sent (over the same encrypted, authenticated channel) from the Coordinator to the signers, possibly the
transaction itself, openings of value commitments, decryption of note
ciphertexts, etc.; and the signers must check that the given SIGHASH matches the
data sent from the Coordinator, or compute the SIGHASH themselves from that
data. However, the specific mechanism for that process is outside the scope of
this ZIP.
more data is needed to be sent (over the same encrypted, authenticated channel)
from the Coordinator to the signers, possibly the transaction itself, openings of
value commitments, decryption of note ciphertexts, etc.; and the signers must check
that the given SIGHASH matches the data sent from the Coordinator, or compute the
SIGHASH themselves from that data. However, the specific mechanism for that process
is outside the scope of this ZIP.
The `sign` function is changed to receive `randomizer_point` and incorporate it
into the computation of the binding factor. It is specified as the following: ::