ZIP 302: Fix references

This commit is contained in:
Kris Nuttycombe 2021-03-18 08:52:55 -06:00
parent 8ac3fa19ea
commit a4e93decc7
1 changed files with 7 additions and 5 deletions

View File

@ -30,10 +30,10 @@ address.
Specification
===============
Section 5.5 of the Zcash protocol specification [#protocol-notept]_ defines three cases
Section 5.5 of the Zcash protocol specification [#protocol]_ defines three cases
for the encoding of a memo field:
* a UTF-8 human-readable string [#Unicode]_, padded by appending zero bytes; or
* a UTF-8 human-readable string [#UTF-8]_, padded by appending zero bytes; or
* the byte ``0xF6`` followed by 511 ``0x00`` bytes, indicating "no memo"; or
* any other sequence of 512 bytes starting with a byte value ``0xF5`` or greater (which is
therefore not a valid UTF-8 string), as specified in ZIP 302.
@ -77,8 +77,6 @@ contents of a memo. It does not define consensus requirements.
type-length-value scheme above, the value of the first byte SHOULD be set to 0xFF; the
remaining 511 bytes are then unconstrained.
See issue `#1849`_ for further discussion.
Rationale
===========
@ -101,6 +99,9 @@ specification that was in the protocol spec up to version 2020.1.0, which stated
byte of 0xF5 is reserved for use by automated software by private agreement. A start
byte of 0xF6 or greater is reserved for use in future Zcash protocol extensions.
See issue `#1849`_ for further discussion.
.. _`#1849`: https://github.com/zcash/zcash/issues/1849
Backwards Compatibility
===========================
@ -111,6 +112,7 @@ interpreted according to the specification set out in older versions of the prot
References
==========
.. [#protocol] `Zcash Protocol Specification, Version 2021.1.19 <protocol/protocol.pdf>`_
.. [#UTF-8] `UTF-8, a transformation format of ISO 10646 <https://tools.ietf.org/html/rfc3629>`_
.. [#Bitcoin-CompactSize] `Variable length integer. Bitcoin Wiki <https://en.bitcoin.it/wiki/Protocol_documentation#Variable_length_integer>`_
.. _`#1849`: https://github.com/zcash/zcash/issues/1849