mirror of https://github.com/zcash/zips.git
Add Human-Readable Parts for UVKs.
Signed-off-by: Daira Hopwood <daira@jacaranda.org>
This commit is contained in:
parent
8c510a1415
commit
5d98ec714a
|
@ -196,6 +196,13 @@ Discussions-To: <<a href="https://github.com/zcash/zips/issues/482">https://g
|
||||||
<span class="math">\(\mathtt{addr}\)</span>
|
<span class="math">\(\mathtt{addr}\)</span>
|
||||||
field is the raw encoding of the Full Viewing Key or Incoming Viewing Key.</p>
|
field is the raw encoding of the Full Viewing Key or Incoming Viewing Key.</p>
|
||||||
<p>Transparent Addresses do not have separate corresponding viewing keys, but the address itself can effectively be used as a viewing key. Therefore, a UFVK or UIVK MAY include a Transparent Address, which is encoded using the same Typecode and Receiver Encoding as in a Unified Address.</p>
|
<p>Transparent Addresses do not have separate corresponding viewing keys, but the address itself can effectively be used as a viewing key. Therefore, a UFVK or UIVK MAY include a Transparent Address, which is encoded using the same Typecode and Receiver Encoding as in a Unified Address.</p>
|
||||||
|
<p>The Human-Readable Parts (as defined in [#bip-0350]) of Unified Viewing Keys are defined as follows:</p>
|
||||||
|
<ul>
|
||||||
|
<li>“<code>uivk</code>” for Unified Incoming Viewing Keys on Mainnet;</li>
|
||||||
|
<li>“<code>uivktest</code>” for Unified Incoming Viewing Keys on Testnet;</li>
|
||||||
|
<li>“<code>uview</code>” for Unified Full Viewing Keys on Mainnet;</li>
|
||||||
|
<li>“<code>uviewtest</code>” for Unified Full Viewing Keys on Testnet.</li>
|
||||||
|
</ul>
|
||||||
</section>
|
</section>
|
||||||
<section id="requirements-for-both-unified-addresses-and-unified-viewing-keys"><h3><span class="section-heading">Requirements for both Unified Addresses and Unified Viewing Keys</span><span class="section-anchor"> <a rel="bookmark" href="#requirements-for-both-unified-addresses-and-unified-viewing-keys"><img width="24" height="24" src="assets/images/section-anchor.png" alt=""></a></span></h3>
|
<section id="requirements-for-both-unified-addresses-and-unified-viewing-keys"><h3><span class="section-heading">Requirements for both Unified Addresses and Unified Viewing Keys</span><span class="section-anchor"> <a rel="bookmark" href="#requirements-for-both-unified-addresses-and-unified-viewing-keys"><img width="24" height="24" src="assets/images/section-anchor.png" alt=""></a></span></h3>
|
||||||
<ul>
|
<ul>
|
||||||
|
|
|
@ -361,6 +361,14 @@ Therefore, a UFVK or UIVK MAY include a Transparent Address, which
|
||||||
is encoded using the same Typecode and Receiver Encoding as in a
|
is encoded using the same Typecode and Receiver Encoding as in a
|
||||||
Unified Address.
|
Unified Address.
|
||||||
|
|
||||||
|
The Human-Readable Parts (as defined in [#bip-0350]) of Unified Viewing
|
||||||
|
Keys are defined as follows:
|
||||||
|
|
||||||
|
* “``uivk``” for Unified Incoming Viewing Keys on Mainnet;
|
||||||
|
* “``uivktest``” for Unified Incoming Viewing Keys on Testnet;
|
||||||
|
* “``uview``” for Unified Full Viewing Keys on Mainnet;
|
||||||
|
* “``uviewtest``” for Unified Full Viewing Keys on Testnet.
|
||||||
|
|
||||||
|
|
||||||
Requirements for both Unified Addresses and Unified Viewing Keys
|
Requirements for both Unified Addresses and Unified Viewing Keys
|
||||||
----------------------------------------------------------------
|
----------------------------------------------------------------
|
||||||
|
|
Loading…
Reference in New Issue