Clarify which transaction fields are added by Overwinter and Sapling.

Signed-off-by: Daira Hopwood <daira@jacaranda.org>
This commit is contained in:
Daira Hopwood 2019-02-22 13:33:39 +00:00
parent 8e9171d512
commit 95d95bc4c4
1 changed files with 4 additions and 0 deletions

View File

@ -8443,6 +8443,9 @@ The changes relative to \Bitcoin version $1$ \transactions as described in \cite
$\nJoinSplit = 0$.
\item The $\nJoinSplit$, $\vJoinSplit$, $\joinSplitPubKey$, and $\joinSplitSig$ fields
have been added.
\overwinteronwarditem{The $\nVersionGroupId$ field has been added.}
\saplingonwarditem{The $\nShieldedSpend$, $\vShieldedSpend$, $\nShieldedOutput$, $\vShieldedOutput$,
and $\bindingSig$ fields have been added.}
\item In \Zcash it is permitted for a \transaction to have no \transparent inputs provided
that $\nJoinSplit > 0$.
\item A consensus rule limiting \transaction size has been added. In \Bitcoin there is
@ -9832,6 +9835,7 @@ Peter Newell's illustration of the Jubjub bird, from \cite{Carroll1902}.
Birthday Problem, and cite \cite{AR2017}.
\item Update reference \cite{BGG2017} (previously [BGG2016]).
\sapling{
\item Clarify which transaction fields are added by \Overwinter and \Sapling.
\item Explain the differences between the system in \cite{Groth2016} and what
we refer to as $\Groth$.
\item Reference Mary Maller's security proof for $\Groth$ \cite{Maller2018}.