mirror of https://github.com/zcash/zips.git
ZIP 316: say how to maximize interoperability by using Revision 0 UA/UVKs
(intentionally without adding any conformance requirement). Signed-off-by: Daira-Emma Hopwood <daira@jacaranda.org>
This commit is contained in:
parent
d28d1d0c24
commit
dfd3ddde28
|
@ -340,6 +340,14 @@ The Human-Readable Parts of Unified Viewing Keys are defined as:
|
|||
* *prefix* || “``view``” for Unified Full Viewing Keys on Mainnet;
|
||||
* *prefix* || “``viewtest``” for Unified Full Viewing Keys on Testnet.
|
||||
|
||||
While support for Revision 1 UAs/UVKs is still being rolled out across
|
||||
the Zcash ecosystem, a Producer can maximize interoperability by
|
||||
generating a Revision 0 UA/UVK in cases where the conditions on its
|
||||
use are met (i.e. there are no MUST-understand Metadata Items, and at
|
||||
least one shielded item). At some point when Revision 1 UA/UVKs are
|
||||
widely supported, this will be unnecessary and it will be sufficient
|
||||
to always produce Revision 1 UA/UVKs.
|
||||
|
||||
|
||||
Encoding of Unified Addresses
|
||||
-----------------------------
|
||||
|
|
Loading…
Reference in New Issue