mirror of https://github.com/zcash/zips.git
Apply suggestions from code review
Co-authored-by: Daira Hopwood <daira@jacaranda.org>
This commit is contained in:
parent
bc16e533af
commit
8fa30b0f44
|
@ -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
|
||||||
|
|
Loading…
Reference in New Issue