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

Final changes to remove undecided parts of the draft

This commit is contained in:
str4d 2021-03-19 11:28:50 +13:00 committed by GitHub
parent eecb7dc43e
commit de694d4509
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 7 additions and 20 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
zip-0302.rst
View File

@ -44,27 +44,14 @@ contents of a memo. It does not define consensus requirements.
+ strip any trailing zero bytes + strip any trailing zero bytes
+ decode it as a UTF-8 string (if decoding fails then report an error). + decode it as a UTF-8 string (if decoding fails then report an error).
+ If the first byte has a value of 0xF5, then the reader MUST: + If the first byte has a value of 0xF6, and the remaining 511 bytes are 0x00, then the user
+ Interpret the next few bytes (1 to 9 of them) as a 64-bit unsigned variable-length supplied no memo, and the encrypted memo field is to be treated as empty.
integer [#Bitcoin-CompactSize]_, and use it as an arbitrary application-defined
"type" field.
+ Interpret the next 1 or 2 bytes as a CompactSize value constrained to the range 0..510, and use
the resulting value as the length of the remaining data.
+ If 1 + the number bytes used for the type field + the number of bytes used for the
length field + the length > 512 then report an error.
+ Inspect the padding after the end of the indicated length, and if it
contains anything other than bytes of value 0x00 then report an error.
+ Return to the caller a 3-tuple of the following data:
+ the type — an integer in :math:`[0...2^{64})`
+ the length — an integer in :math:`[0...510)`
+ a byte string of that length that contains the payload
+ If the first byte has a value of 0xF6, then the user supplied no memo, and the encrypted + If the memo matches any of these patterns, then this memo is from the future, because
memo field is to be treated as empty. these ranges are reserved for future updates to this specification:
- The first byte has a value of 0xF5.
+ If the first byte has a value between 0xF7 and 0xFE inclusive, then this memo is from - The first byte has a value between 0xF7 and 0xFE inclusive.
the future, because first byte values of 0xF7–0xFE are reserved for future - The first byte has a value of 0xF6, and the remaining 511 bytes are not all 0x00.
specifications of this protocol.
+ If the first byte has a value of 0xFF then the reader should not make any other + If the first byte has a value of 0xFF then the reader should not make any other
assumption about the memo. In order to put data into a memo field that does not use the assumption about the memo. In order to put data into a memo field that does not use the