ZIP 316: Clarify requirements for HD-derived items and remove redundancy.

Signed-off-by: Daira Hopwood <daira@jacaranda.org>
This commit is contained in:
Daira Hopwood 2021-12-08 00:25:45 +00:00
parent 208d9b39c1
commit 0e83a55a05
1 changed files with 3 additions and 6 deletions

View File

@ -445,12 +445,9 @@ Requirements for both Unified Addresses and Unified Viewing Keys
all less than 256 bytes and so could use a one-byte length field,
encodings for experimental types may be longer.)
* Each Receiver and FVK SHOULD represent an Address or Full Viewing
Key at the ZIP 32 or BIP 44 Account level.
* Each IVK SHOULD represent an Incoming Viewing Key at the Account
level for Sapling or Orchard, or its non-change child extended public
key for Transparent P2PKH.
* Within a single UA or UVK, all HD-derived Receivers, FVKs, and IVKs
SHOULD represent an Address or Viewing Key for the same account (as
used in the ZIP 32 or BIP 44 Account level).
* For Transparent Addresses, the Receiver Encoding does not include
the first two bytes of a raw encoding.