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

ZIP 316: Clarify wording for UFVK or UIVK Encoding, and the reason why P2SH UFVK/UIVKs are not supported. 

Signed-off-by: Daira Hopwood <daira@jacaranda.org>
This commit is contained in:
Daira Hopwood 2021-09-17 14:37:02 +01:00
parent 0e057c3c8c
commit 39998c226c
1 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
zip-0316.rst
View File

@ -389,8 +389,8 @@ The following UFVK or UIVK Encodings are used in place of the
:math:`\mathtt{addr}` field:
* An Orchard UFVK or UIVK Encoding, with Typecode :math:`\mathtt{0x03},`
is the raw encoding of the Full Viewing Key or Incoming Viewing Key
respectively.
is the raw encoding of the Orchard Full Viewing Key or Orchard Incoming
Viewing Key respectively.
* A Sapling UFVK Encoding, with Typecode :math:`\mathtt{0x02},` is
the encoding of a Sapling Extended Full Viewing Key defined in
@ -400,9 +400,10 @@ The following UFVK or UIVK Encodings are used in place of the
is an encoding of :math:`(\mathsf{dk}, \mathsf{ivk})` given by
:math:`\mathsf{I2LEOSP}_{88}(\mathsf{dk})\,||\,\mathsf{I2LEOSP}_{256}(\mathsf{ivk}).`
* There is no defined way to represent a viewing key for a Transparent
P2SH Address in a UFVK or UIVK. The Typecode :math:`\mathtt{0x01}`
MUST not be included in a UFVK or UIVK by Producers, and MUST be
* There is no defined way to represent a Viewing Key for a Transparent
P2SH Address in a UFVK or UIVK (because P2SH Addresses cannot be
diversified in an unlinkable way). The Typecode :math:`\mathtt{0x01}`
MUST NOT be included in a UFVK or UIVK by Producers, and MUST be
treated as unrecognized by Consumers.
* For Transparent P2PKH Addresses that are derived according to BIP 32