From 8fa30b0f4455d1383ab2322a66760b7c3849b3c8 Mon Sep 17 00:00:00 2001 From: Conrado Gouvea Date: Mon, 16 Jan 2023 19:03:20 -0300 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Daira Hopwood --- zip-0312.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/zip-0312.rst b/zip-0312.rst index 934763b8..66663400 100644 --- a/zip-0312.rst +++ b/zip-0312.rst @@ -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.) 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, -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 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