Correct the number of bytes in the encoding of solutionSize.

Signed-off-by: Daira Hopwood <daira@jacaranda.org>

protocol/protocol.tex

@@ -2849,7 +2849,7 @@ header hash must be less than or equal to, in the same nBits format used by \Bit
 32 & $\nNonce$ & \type{char[32]} & An arbitrary field miners change to modify the
 header hash in order to produce a hash below the target threshold. \\ \hline
 
-2 & $\solutionSize$ & \compactSize & The size of an Equihash solution in bytes (always 1344). \\ \hline
+3 & $\solutionSize$ & \compactSize & The size of an Equihash solution in bytes (always 1344). \\ \hline
 
 1344 & $\solution$ & \type{char[1344]} & The Equihash solution, which \MUST be valid
 according to \crossref{equihash}. \\ \hline
@@ -2871,7 +2871,7 @@ The changes relative to \Bitcoin version 4 blocks as described in \cite{Bitcoin-
   \item There is no relation between the values of the $\versionField$ field of a \transaction,
         and the $\nVersion$ field of a \blockHeader.
   \item Like other serialized fields of type $\compactSize$, the $\solutionSize$ field \MUST
-        be encoded with the minimum number of bytes (2 in this case), and other encodings
+        be encoded with the minimum number of bytes (3 in this case), and other encodings
         \MUST be rejected. This is necessary to avoid a potential attack in which a miner
         could test several distinct encodings of each Equihash solution against the difficulty
         filter, rather than only the single intended encoding.
@@ -3545,6 +3545,7 @@ The errors in the proof of Ledger Indistinguishability mentioned in
 \subparagraph{2016.0-beta-1.6}
 
 \begin{itemize}
+    \item Correct the number of bytes in the encoding of $\solutionSize$.
     \item Update the section on encoding of \transparent addresses.
           (The precise prefixes are not decided yet.)
     \item Add a paragraph about key length in \crossref{inbandrationale}.