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

Apply suggestions from code review 

Co-authored-by: Daira Hopwood <daira@jacaranda.org>
This commit is contained in:
Conrado Gouvea 2023-01-16 19:03:20 -03:00 committed by GitHub
parent bc16e533af
commit 8fa30b0f44
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
zip-0312.rst
View File

@ -217,9 +217,9 @@ along with the message and the set of signing commitments. (Note that this diffe
from regular FROST which just requires an authenticated channel.) from regular FROST which just requires an authenticated channel.)
In Zcash, the message that needs to be signed is actually the SIGHASH In Zcash, the message that needs to be signed is actually the SIGHASH
transaction hash, which is does not convey enough information for the signers to 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, decide if they want to authorize the transaction or not. Therefore, in practice,
more data is needed to be sent from the Coordinator to the signers, possibly the 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 transaction itself, openings of value commitments, decryption of note
ciphertexts, etc.; and the signers must check that the given SIGHASH matches the 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 sent from the Coordinator, or compute the SIGHASH themselves from that