Specify that 0xF6 followed by zeros encodes an empty memo.

Signed-off-by: Daira Hopwood <daira@jacaranda.org>
This commit is contained in:
Daira Hopwood 2018-02-07 11:09:50 +00:00
parent a11f8a5fe0
commit de60c26bb9
1 changed files with 5 additions and 2 deletions

View File

@ -3866,8 +3866,9 @@ Incorrect UTF-8-encoded byte sequences should be displayed as replacement charac
In the latter case, the contents of the \memo{} \SHOULDNOT be displayed. A start byte
of $\hexint{F5}$ is reserved for use by automated software by private agreement.
A start byte of $\hexint{F6}$ or greater is reserved for use in future \Zcash
protocol extensions.
A start byte of $\hexint{F6}$ followed by $511$ $\hexint{00}$ bytes means ``no memo''.
A start byte of $\hexint{F6}$ followed by anything else, or a start byte of $\hexint{F7}$
or greater, are reserved for use in future \Zcash protocol extensions.
}
\introlist
@ -5504,6 +5505,8 @@ The errors in the proof of Ledger Indistinguishability mentioned in
\begin{itemize}
\item Specify the $100000$-byte limit on \transaction size.
(The implementation in \zcashd was as intended.)
\item Specify that $\hexint{F6}$ followed by $511$ zero bytes encodes an
empty \memo.
\item Rename $\mathsf{clamp}$ to $\mathsf{bound}$ and
$\mathsf{ActualTimespanClamped}$ to $\ActualTimespanBounded$
in the difficulty adjustment algorithm, to avoid a name