From 5a4aefb58e842091ba042cb2adde99fc1dd020dc Mon Sep 17 00:00:00 2001 From: Daira Hopwood Date: Thu, 13 Jan 2022 14:25:50 +0000 Subject: [PATCH] Apply suggestions from code review Minor wording nits. --- zip-0244.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/zip-0244.rst b/zip-0244.rst index bb09ebc00..4640cfcc4 100644 --- a/zip-0244.rst +++ b/zip-0244.rst @@ -845,10 +845,10 @@ align with BIP 341 [#bip-0341]_: P2SH (where ``scriptPubKey`` is fully executed prior to ``redeemScript``). - For P2SH, this means we commit to the Hash160 digest of ``redeemScript`` instead of the actual script. Note that the Bitcoin P2SH design depends - entirely on Hash160 being preimage resistant, because otherwise anyone would + entirely on Hash160 being preimage-resistant, because otherwise anyone would be able to spend someone else's P2SH UTXO using a preimage. We do need to ensure that there is no collision attack; this holds because even if an - adversary could find a Hash160 collision, this would only enable them to + adversary could find a Hash160 collision, it would only enable them to alter the input's ``scriptSig`` field. Doing so doesn't alter the effecting data of the transaction, which by definition means the transaction has the same effect under consensus (spends the same inputs and produces the same