mirror of https://github.com/zcash/zips.git
ZIP 155: regenerate HTML.
Signed-off-by: Daira Hopwood <daira@jacaranda.org>
This commit is contained in:
Daira Hopwood
parent
a9fa1f4d18
commit
fc6e752b05
|
|
@ -22,16 +22,17 @@ Pull-Request: <<a href="https://github.com/zcash/zips/pull/543">https://githu
|
|||
<p>The term "network upgrade" in this document is to be interpreted as described in ZIP 200. <a id="id2" class="footnote_reference" href="#zip-0200">4</a></p>
|
||||
<p>The terms "Testnet" and "Mainnet" are to be interpreted as described in section 3.11 of the Zcash Protocol Specification <a id="id3" class="footnote_reference" href="#protocol-networks">2</a>.</p>
|
||||
<p>"P2P network" means the Zcash peer-to-peer network.</p>
|
||||
<p><code>uint8</code>, <code>uint16</code>, and <code>uint32</code> denote unsigned integer data types of the corresponding length (8, 16, or 32 bits respectively).</p>
|
||||
</section>
|
||||
<section id="abstract"><h2><span class="section-heading">Abstract</span><span class="section-anchor"> <a rel="bookmark" href="#abstract"><img width="24" height="24" src="assets/images/section-anchor.png" alt=""></a></span></h2>
|
||||
<p>This document proposes a new P2P message to gossip longer node addresses over the P2P network. This is required to support new-generation Onion addresses, I2P, and potentially other networks that have longer endpoint addresses than fit in the 128 bits of the current <code>addr</code> message.</p>
|
||||
<p>This document proposes a new P2P message to gossip longer node addresses over the P2P network. This is required to support new-generation onion addresses, I2P, and potentially other networks that have longer endpoint addresses than fit in the 128 bits of the current <code>addr</code> message.</p>
|
||||
</section>
|
||||
<section id="motivation"><h2><span class="section-heading">Motivation</span><span class="section-anchor"> <a rel="bookmark" href="#motivation"><img width="24" height="24" src="assets/images/section-anchor.png" alt=""></a></span></h2>
|
||||
<p>Tor v3 hidden services are part of the stable release of Tor since version 0.3.2.9. They have various advantages compared to the old hidden services, among which better encryption and privacy <a id="id4" class="footnote_reference" href="#tor-rendezvous-v3">9</a>. These services have 256-bit addresses and thus do not fit in the existing <code>addr</code> message, which encapsulates onion addresses in OnionCat IPv6 addresses.</p>
|
||||
<p>Tor v3 onion services are part of the stable release of Tor since version 0.3.2.9. They have various advantages compared to the old v2 onion services, among which better encryption and privacy <a id="id4" class="footnote_reference" href="#tor-rendezvous-v3">9</a>. These services have 256-bit addresses and thus do not fit in the existing <code>addr</code> message (unchanged from Bitcoin <a id="id5" class="footnote_reference" href="#bitcoin-addr-message">7</a>), which encapsulates onion addresses in OnionCat IPv6 addresses.</p>
|
||||
<p>Other transport-layer protocols such as I2P have always used longer addresses. This change would make it possible to gossip such addresses over the P2P network, so that other peers can connect to them.</p>
|
||||
</section>
|
||||
<section id="specification"><h2><span class="section-heading">Specification</span><span class="section-anchor"> <a rel="bookmark" href="#specification"><img width="24" height="24" src="assets/images/section-anchor.png" alt=""></a></span></h2>
|
||||
<p>The <code>addrv2</code> message is defined as a message where <code>pchCommand == "addrv2"</code>. It is serialized in the standard encoding for P2P messages. Its format is similar to the current <code>addr</code> message format described in <a id="id5" class="footnote_reference" href="#bitcoin-addr-message">7</a>, with the difference that the fixed 16-byte IP address is replaced by a network ID and a variable-length address, and the services format has been changed to <a id="id6" class="footnote_reference" href="#bitcoin-compactsize">8</a>.</p>
|
||||
<p>The <code>addrv2</code> message is defined as a message where the <code>command</code> field is (NUL-padded) <code>"addrv2"</code>. It is serialized in the standard encoding for P2P messages. Its format is similar to the current <code>addr</code> message format described in <a id="id6" class="footnote_reference" href="#bitcoin-addr-message">7</a>, with the difference that the fixed 16-byte IP address is replaced by a network ID and a variable-length address, and the services format has been changed to <a id="id7" class="footnote_reference" href="#bitcoin-compactsize">8</a>.</p>
|
||||
<p>This means that the message contains a serialized vector of the following structure:</p>
|
||||
<blockquote>
|
||||
<table>
|
||||
|
|
@ -82,7 +83,7 @@ Pull-Request: <<a href="https://github.com/zcash/zips/pull/543">https://githu
|
|||
</table>
|
||||
</blockquote>
|
||||
<p>One message can contain up to 1,000 addresses. Clients MUST reject messages with more addresses.</p>
|
||||
<p>Field <code>addr</code> has a variable length, with a maximum of 512 bytes (4096 bits). Clients SHOULD reject messages with longer addresses, irrespective of the network ID.</p>
|
||||
<p>Field <code>addr</code> has a variable length, with a maximum of 512 bytes (4096 bits). Clients MUST reject messages with a longer <code>addr</code> field, irrespective of the network ID.</p>
|
||||
<p>The list of reserved network IDs is as follows:</p>
|
||||
<blockquote>
|
||||
<table>
|
||||
|
|
@ -109,7 +110,7 @@ Pull-Request: <<a href="https://github.com/zcash/zips/pull/543">https://githu
|
|||
<td><code>0x04</code></td>
|
||||
<td><code>TORV3</code></td>
|
||||
<td>32</td>
|
||||
<td>Tor v3 hidden service address</td>
|
||||
<td>Tor v3 onion service address</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>0x05</code></td>
|
||||
|
|
@ -126,57 +127,56 @@ Pull-Request: <<a href="https://github.com/zcash/zips/pull/543">https://githu
|
|||
</tbody>
|
||||
</table>
|
||||
</blockquote>
|
||||
<p>Network ID <code>0x03</code> is intentionally not assigned. In BIP 155 <a id="id7" class="footnote_reference" href="#bip-0155">3</a> it was assigned to Tor v2 hidden service addresses, but those addresses are no longer supported by the latest Tor client code, and MUST NOT be used once this ZIP is deployed.</p>
|
||||
<p>Network ID <code>0x03</code> is intentionally not assigned. In BIP 155 <a id="id8" class="footnote_reference" href="#bip-0155">3</a> it was assigned to Tor v2 onion addresses, but those addresses are no longer supported by the latest Tor client code, and MUST NOT be used once this ZIP is deployed.</p>
|
||||
<p>Clients SHOULD gossip addresses from all known networks even if they are currently not connected to some of them. That could help multi-homed nodes and make it more difficult for an observer to tell which networks a node is connected to.</p>
|
||||
<p>Clients MUST NOT gossip addresses from unknown networks, because they have no means to validate those addresses and so can be tricked to gossip invalid addresses.</p>
|
||||
<p>Further network ID numbers MUST be reserved in a new ZIP.</p>
|
||||
<p>Clients MUST reject messages that contain addresses that have a different length than specified in this table for a specific network ID, as these are meaningless.</p>
|
||||
<section id="network-address-encodings"><h3><span class="section-heading">Network address encodings</span><span class="section-anchor"> <a rel="bookmark" href="#network-address-encodings"><img width="24" height="24" src="assets/images/section-anchor.png" alt=""></a></span></h3>
|
||||
<p>The <code>IPV4</code> and <code>IPV6</code> network IDs use addresses encoded in the usual way for binary IPv4 and IPv6 addresses in network byte order (big endian).</p>
|
||||
<section id="tor-v3-address-encoding"><h4><span class="section-heading">Tor v3 address encoding</span><span class="section-anchor"> <a rel="bookmark" href="#tor-v3-address-encoding"><img width="24" height="24" src="assets/images/section-anchor.png" alt=""></a></span></h4>
|
||||
<p>According to the spec <a id="id8" class="footnote_reference" href="#tor-rendezvous-v3">9</a>, version 3 <code>.onion</code> addresses are encoded as follows:</p>
|
||||
<pre>onion_address = base32(PUBKEY | CHECKSUM | VERSION) + ".onion"
|
||||
CHECKSUM = H(".onion checksum" | PUBKEY | VERSION)[:2]</pre>
|
||||
<p>According to the spec <a id="id9" class="footnote_reference" href="#tor-rendezvous-v3">9</a>, version 3 <code>.onion</code> addresses are encoded as follows:</p>
|
||||
<pre>onion_address = base32(PUBKEY || CHECKSUM || VERSION) + ".onion"
|
||||
CHECKSUM = H(".onion checksum" || PUBKEY || VERSION)[:2] // first 2 bytes</pre>
|
||||
<p>where:</p>
|
||||
<ul>
|
||||
<li><code>PUBKEY</code> is the 32 bytes Ed25519 master pubkey of the hidden service;</li>
|
||||
<li><code>VERSION</code> is a one byte version field (default value <code>0x03</code>);</li>
|
||||
<li><code>PUBKEY</code> is the 32-byte Ed25519 master pubkey of the onion service;</li>
|
||||
<li><code>VERSION</code> is a one-byte version field (default value <code>0x03</code>);</li>
|
||||
<li><code>".onion"</code> and <code>".onion checksum"</code> are constant strings;</li>
|
||||
<li><code>CHECKSUM</code> is truncated to two bytes before inserting it in <code>onion_address</code>;</li>
|
||||
<li><code>H()</code> is the SHA3-256 cryptographic hash function.</li>
|
||||
<li><code>H()</code> is the SHA3-256 cryptographic hash function. <a id="id10" class="footnote_reference" href="#nist-sha3">10</a></li>
|
||||
</ul>
|
||||
<p>Tor v3 addresses MUST be sent with the <code>TORV3</code> network ID, with the 32-byte <code>PUBKEY</code> part in the address field. As <code>VERSION</code> will always be 'x03' in the case of v3 addresses, this is enough to reconstruct the onion address.</p>
|
||||
<p>Tor v3 addresses MUST be sent with the <code>TORV3</code> network ID, with the 32-byte <code>PUBKEY</code> part in the <code>addr</code> field. As <code>VERSION</code> will always be 0x03 in the case of v3 addresses, this is enough to reconstruct the onion address.</p>
|
||||
</section>
|
||||
<section id="i2p-address-encoding"><h4><span class="section-heading">I2P address encoding</span><span class="section-anchor"> <a rel="bookmark" href="#i2p-address-encoding"><img width="24" height="24" src="assets/images/section-anchor.png" alt=""></a></span></h4>
|
||||
<p>Like Tor, I2P naming uses a base32-encoded address format <a id="id9" class="footnote_reference" href="#i2p-naming">10</a>.</p>
|
||||
<p>I2P uses 52 characters (256 bits) to represent the full SHA-256 hash, followed by <code>.b32.i2p</code>.</p>
|
||||
<p>Like Tor, I2P naming uses a base32-encoded address format <a id="id11" class="footnote_reference" href="#i2p-naming">11</a>.</p>
|
||||
<p>I2P uses 52 characters (256 bits) to represent the full SHA-256 hash, followed by <code>.b32.i2p</code>. The base32 encoding does not include <code>"="</code> padding characters.</p>
|
||||
<p>I2P addresses MUST be sent with the <code>I2P</code> network ID, with the decoded SHA-256 hash as address field.</p>
|
||||
</section>
|
||||
<section id="cjdns-address-encoding"><h4><span class="section-heading">Cjdns address encoding</span><span class="section-anchor"> <a rel="bookmark" href="#cjdns-address-encoding"><img width="24" height="24" src="assets/images/section-anchor.png" alt=""></a></span></h4>
|
||||
<p>Cjdns addresses are simply IPv6 addresses in the <code>fc00::/8</code> range <a id="id10" class="footnote_reference" href="#cjdns-whitepaper">11</a>. They MUST be sent with the <code>CJDNS</code> network ID.</p>
|
||||
<p>Cjdns addresses are simply IPv6 addresses in the <code>fc00::/8</code> range <a id="id12" class="footnote_reference" href="#cjdns-whitepaper">12</a>. They MUST be sent with the <code>CJDNS</code> network ID. They are encoded in network byte order (big endian) as for the <code>IPV6</code> network ID.</p>
|
||||
</section>
|
||||
</section>
|
||||
<section id="deployment"><h3><span class="section-heading">Deployment</span><span class="section-anchor"> <a rel="bookmark" href="#deployment"><img width="24" height="24" src="assets/images/section-anchor.png" alt=""></a></span></h3>
|
||||
<p>Support for this specification is signalled by peer protocol version 170015 (on both Testnet and Mainnet). Note that this is the same peer protocol version that signals support for NU5 on Mainnet <a id="id11" class="footnote_reference" href="#zip-0252">6</a>.</p>
|
||||
<p>Support for this specification is signalled by peer protocol version 170015 (on both Testnet and Mainnet). Note that this is the same peer protocol version that signals support for NU5 on Mainnet <a id="id13" class="footnote_reference" href="#zip-0252">6</a>.</p>
|
||||
<p>Nodes that have not negotiated peer protocol version 170015 or higher on a given connection, MUST NOT send <code>addrv2</code> messages on that connection.</p>
|
||||
<p>A node that has negotiated peer protocol version 170015 or higher on a given connection, MAY still send <code>addr</code> messages on the connection, and MUST handle received <code>addr</code> messages as it would have done prior to this ZIP.</p>
|
||||
</section>
|
||||
</section>
|
||||
<section id="rationale"><h2><span class="section-heading">Rationale</span><span class="section-anchor"> <a rel="bookmark" href="#rationale"><img width="24" height="24" src="assets/images/section-anchor.png" alt=""></a></span></h2>
|
||||
<p>This ZIP is closely based on BIP 155 <a id="id12" class="footnote_reference" href="#bip-0155">3</a>, with the following changes:</p>
|
||||
<p>This ZIP is closely based on BIP 155 <a id="id14" class="footnote_reference" href="#bip-0155">3</a>, with the following changes:</p>
|
||||
<ul>
|
||||
<li>Deployment: support for the <code>addrv2</code> message is signalled by advertising a peer-to-peer protocol version of 170015 or higher, not by sending a <code>sendaddrv2</code> message. This is motivated by a desire to avoid an exponential explosion in the space of possible feature configurations in a given peer-to-peer connection. In Zcash, unlike Bitcoin, the space of such configurations is effectively constant no matter how many peer-to-peer protocol changes are made, because nodes that do not support a given peer protocol version will drop off the network over time if they do not support the latest Network Upgrade. The feature configuration for a given connection is also established at version negotiation, and cannot change after that point without reconnecting. Other peer-to-peer protocol changes ported from the Bitcoin peer-to-peer protocol, for example the <code>MSG_WTX</code> inv type defined in ZIP 239 <a id="id13" class="footnote_reference" href="#zip-0239">5</a>, have taken the same approach to signalling.</li>
|
||||
<li>No Network ID for Tor v2 hidden service addresses: the Tor network is expected to have removed support for these addresses in the timeframe for deployment of this ZIP.</li>
|
||||
<li>Deployment: support for the <code>addrv2</code> message is signalled by advertising a peer protocol version of 170015 or higher, not by sending a <code>sendaddrv2</code> message. This is motivated by a desire to avoid an exponential explosion in the space of possible feature configurations in a given peer-to-peer connection. In Zcash, unlike Bitcoin, the space of such configurations is effectively constant no matter how many peer-to-peer protocol changes are made, because nodes that do not support a given peer protocol version will drop off the network over time if they do not support the latest Network Upgrade. The feature configuration for a given connection is also established at version negotiation, and cannot change after that point without reconnecting. Other peer-to-peer protocol changes ported from the Bitcoin peer-to-peer protocol, for example the <code>MSG_WTX</code> inv type defined in ZIP 239 <a id="id15" class="footnote_reference" href="#zip-0239">5</a>, have taken the same approach to signalling.</li>
|
||||
<li>No Network ID for Tor v2 onion addresses: the Tor network is expected to have removed support for these addresses in the timeframe for deployment of this ZIP.</li>
|
||||
<li>Clients MUST, rather than SHOULD, reject <code>addrv2</code> messages with more than 1,000 addresses. Making this a consistent requirement promotes interoperability.</li>
|
||||
<li>Clients MUST NOT, rather than SHOULD NOT, gossip addresses from unknown networks.</li>
|
||||
<li>Clients MUST, rather than SHOULD, reject messages that contain addresses that have a different length than specified for a specific network ID.</li>
|
||||
<li>Clients MUST, rather than SHOULD, reject messages that contain addresses that have a different length than specified for a known network ID, or a length greater than the 512-byte maximum for an unknown network ID.</li>
|
||||
</ul>
|
||||
</section>
|
||||
<section id="reference-implementation"><h2><span class="section-heading">Reference implementation</span><span class="section-anchor"> <a rel="bookmark" href="#reference-implementation"><img width="24" height="24" src="assets/images/section-anchor.png" alt=""></a></span></h2>
|
||||
<p>TBD.</p>
|
||||
</section>
|
||||
<section id="acknowledgements"><h2><span class="section-heading">Acknowledgements</span><span class="section-anchor"> <a rel="bookmark" href="#acknowledgements"><img width="24" height="24" src="assets/images/section-anchor.png" alt=""></a></span></h2>
|
||||
<p>This ZIP is closely based on BIP 155 <a id="id14" class="footnote_reference" href="#bip-0155">3</a>, written by Wladimir J. van der Laan. Zancas Wilcox ported the implementation for Zcashd.</p>
|
||||
<p>This ZIP is closely based on BIP 155 <a id="id16" class="footnote_reference" href="#bip-0155">3</a>, written by Wladimir J. van der Laan. Zancas Wilcox ported the implementation for Zcashd.</p>
|
||||
<p>Acknowledgements for BIP 155:</p>
|
||||
<ul>
|
||||
<li>Jonas Schnelli: change <code>services</code> field to <code>CompactSize</code>, to make the message more compact in the likely case instead of always using 8 bytes.</li>
|
||||
|
|
@ -256,10 +256,18 @@ CHECKSUM = H(".onion checksum" | PUBKEY | VERSION)[:2]</pre>
|
|||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<table id="i2p-naming" class="footnote">
|
||||
<table id="nist-sha3" class="footnote">
|
||||
<tbody>
|
||||
<tr>
|
||||
<th>10</th>
|
||||
<td><a href="https://csrc.nist.gov/publications/detail/fips/202/final">NIST FIPS 202 - SHA-3 Standard: Permutation-Based Hash and Extendable-Output Functions</a></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<table id="i2p-naming" class="footnote">
|
||||
<tbody>
|
||||
<tr>
|
||||
<th>11</th>
|
||||
<td><a href="https://geti2p.net/en/docs/naming#base32">I2P: Naming and address book</a></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
|
|
@ -267,7 +275,7 @@ CHECKSUM = H(".onion checksum" | PUBKEY | VERSION)[:2]</pre>
|
|||
<table id="cjdns-whitepaper" class="footnote">
|
||||
<tbody>
|
||||
<tr>
|
||||
<th>11</th>
|
||||
<th>12</th>
|
||||
<td><a href="https://github.com/cjdelisle/cjdns/blob/f909b960709a4e06730ddd4d221e5df38164dbb6/doc/Whitepaper.md#pulling-it-all-together">Cjdns whitepaper: Pulling It All Together</a></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
|
|
|
|||
Loading…
Reference in New Issue