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

Add [Canopy onward] and [NU5 onward] to a couple of notes. 

Signed-off-by: Daira Hopwood <daira@jacaranda.org>
This commit is contained in:
Daira Hopwood 2021-05-07 12:08:49 +01:00
parent e4af6e42a0
commit 4353accc0e
1 changed files with 5 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
protocol/protocol.tex
View File

@ -12438,14 +12438,11 @@ each \spendDescription\, (\crossref{spendencodingandconsensus}),\,\notnufive{ an
to spend coinbase outputs only in \transactions with no \transparent outputs, applied to to spend coinbase outputs only in \transactions with no \transparent outputs, applied to
\emph{all} coinbase outputs. \emph{all} coinbase outputs.
} %heartwood } %heartwood
\canopy{ \canopyonwarditem{The rule that \Sapling outputs in \coinbaseTransactions \MUST decrypt to a \notePlaintext
\item The rule that \Sapling outputs in \coinbaseTransactions \MUST decrypt to a \notePlaintext
with lead byte $\hexint{02}$, also applies to \fundingStream outputs that specify \Sapling with lead byte $\hexint{02}$, also applies to \fundingStream outputs that specify \Sapling
\shieldedPaymentAddresses, if there are any. \shieldedPaymentAddresses, if there are any.}
} %canopy \nufiveonwarditem{The flags in \flagsOrchard{} allow a version 5 \transaction to declare that no funds are
\nufive{ spent from \Orchard \notes (by setting \enableSpendsOrchard{} to $0$), or that no new \Orchard \notes
\item The flags in \flagsOrchard{} allow a version 5 \transaction to declare that no funds are spent
from \Orchard \notes (by setting \enableSpendsOrchard{} to $0$), or that no new \Orchard \notes
with nonzero values are created (by setting \enableOutputsOrchard{} to $0$). This has two primary with nonzero values are created (by setting \enableOutputsOrchard{} to $0$). This has two primary
purposes. First, the \enableSpendsOrchard{} flag is set to $0$ in version 5 \coinbaseTransactions to purposes. First, the \enableSpendsOrchard{} flag is set to $0$ in version 5 \coinbaseTransactions to
ensure that they cannot spend from existing \Orchard outputs. This maintains a restriction present ensure that they cannot spend from existing \Orchard outputs. This maintains a restriction present
@ -12457,8 +12454,7 @@ each \spendDescription\, (\crossref{spendencodingandconsensus}),\,\notnufive{ an
only on the relevant side. Setting either of these flags to $0$ does not affect the presence or only on the relevant side. Setting either of these flags to $0$ does not affect the presence or
validation of \spendAuthSignatures, or other consensus rules associated with \actionDescriptions. validation of \spendAuthSignatures, or other consensus rules associated with \actionDescriptions.
These \note spending and creation consensus rules are specified as part of the \Orchard These \note spending and creation consensus rules are specified as part of the \Orchard
\actionStatement (\crossref{actionstatement}). \actionStatement (\crossref{actionstatement}).}
} %nufive
\nufiveonwarditem{Because \enableSpendsOrchard{} is set to $0$ in version 5 \coinbaseTransactions\ --which \nufiveonwarditem{Because \enableSpendsOrchard{} is set to $0$ in version 5 \coinbaseTransactions\ --which
disables non-zero-valued \Orchard spends-- the $\valueBalance{Orchard}$ field of a \coinbaseTransaction disables non-zero-valued \Orchard spends-- the $\valueBalance{Orchard}$ field of a \coinbaseTransaction
must have a negative or zero value. The negative case can only occur for \transactions with must have a negative or zero value. The negative case can only occur for \transactions with