ZIP 243: clarify in "Backward compatibility" that the reason why the ZIP 243 sighash algorithm

is used for all transactions from Sapling activation, is that v3 transactions are no longer valid.

Signed-off-by: Daira Hopwood <daira@jacaranda.org>
This commit is contained in:
Daira Hopwood 2022-01-11 13:06:51 +00:00
parent 8572075604
commit 3ba7b5f246
2 changed files with 4 additions and 3 deletions

View File

@ -437,7 +437,7 @@ vJoinSplit: 00</pre>
<p>This proposal is deployed with the Sapling network upgrade. <a id="id14" class="footnote_reference" href="#zip-0205">6</a></p> <p>This proposal is deployed with the Sapling network upgrade. <a id="id14" class="footnote_reference" href="#zip-0205">6</a></p>
</section> </section>
<section id="backward-compatibility"><h2><span class="section-heading">Backward compatibility</span><span class="section-anchor"> <a rel="bookmark" href="#backward-compatibility"><img width="24" height="24" src="assets/images/section-anchor.png" alt=""></a></span></h2> <section id="backward-compatibility"><h2><span class="section-heading">Backward compatibility</span><span class="section-anchor"> <a rel="bookmark" href="#backward-compatibility"><img width="24" height="24" src="assets/images/section-anchor.png" alt=""></a></span></h2>
<p>This proposal is backwards-compatible with old UTXOs. It is <strong>not</strong> backwards-compatible with older software. All transactions will be required to use this transaction digest algorithm for signatures, and so transactions created by older software will be rejected by the network.</p> <p>This proposal is backwards-compatible with old UTXOs. It is <strong>not</strong> backwards-compatible with older software. Given that v3 transaction formats will be invalid from the Sapling upgrade, all transactions will be required to use this transaction digest algorithm for signatures, and so transactions created by older software will be rejected by the network.</p>
</section> </section>
<section id="reference-implementation"><h2><span class="section-heading">Reference Implementation</span><span class="section-anchor"> <a rel="bookmark" href="#reference-implementation"><img width="24" height="24" src="assets/images/section-anchor.png" alt=""></a></span></h2> <section id="reference-implementation"><h2><span class="section-heading">Reference Implementation</span><span class="section-anchor"> <a rel="bookmark" href="#reference-implementation"><img width="24" height="24" src="assets/images/section-anchor.png" alt=""></a></span></h2>
<p><a href="https://github.com/zcash/zcash/pull/3233">https://github.com/zcash/zcash/pull/3233</a></p> <p><a href="https://github.com/zcash/zcash/pull/3233">https://github.com/zcash/zcash/pull/3233</a></p>

View File

@ -513,8 +513,9 @@ Backward compatibility
====================== ======================
This proposal is backwards-compatible with old UTXOs. It is **not** backwards-compatible with older software. This proposal is backwards-compatible with old UTXOs. It is **not** backwards-compatible with older software.
All transactions will be required to use this transaction digest algorithm for signatures, and so transactions Given that v3 transaction formats will be invalid from the Sapling upgrade, all transactions will be required
created by older software will be rejected by the network. to use this transaction digest algorithm for signatures, and so transactions created by older software will
be rejected by the network.
Reference Implementation Reference Implementation