diff options
| author | MarcoFalke <falke.marco@gmail.com> | 2017-12-19 13:52:46 -0500 |
|---|---|---|
| committer | MarcoFalke <falke.marco@gmail.com> | 2017-12-19 13:52:25 -0500 |
| commit | fa810b3bff542200c50c4fd33fcfd982142b63ed (patch) | |
| tree | a7ccc16dc8d40e71843d2a477f3f2f5d780de6f1 | |
| parent | 2e1813abdc213afc8a05f8f2ce34f3d118d7ba82 (diff) | |
| download | bips-fa810b3bff542200c50c4fd33fcfd982142b63ed.tar.xz | |
bip159: Clarify that there is only one threshold
| -rw-r--r-- | bip-0159.mediawiki | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/bip-0159.mediawiki b/bip-0159.mediawiki index 79fd0fc..9c880ed 100644 --- a/bip-0159.mediawiki +++ b/bip-0159.mediawiki @@ -31,10 +31,10 @@ This BIP proposes a new service bit {|class="wikitable" |- -| NODE_NETWORK_LIMITED || bit 10 (0x400) || If signaled, the peer <I>MUST</I> be capable of serving at least the last 288 blocks (~2 day / the current minimum limit for Bitcoin Core). +| NODE_NETWORK_LIMITED || bit 10 (0x400) || If signaled, the peer <I>MUST</I> be capable of serving at least the last 288 blocks (~2 days). |} -A safety buffer of additional 144 blocks to handle chain reorganizations <I>SHOULD</I> be taken into account when connecting to a peer signaling the <code>NODE_NETWORK_LIMITED</code> service bit. +A safety buffer of 144 blocks to handle chain reorganizations <I>SHOULD</I> be taken into account when connecting to a peer signaling the <code>NODE_NETWORK_LIMITED</code> service bit. === Address relay === @@ -42,7 +42,7 @@ Full nodes following this BIP <I>SHOULD</I> relay address/services (<code>addr</ === Counter-measures for peer fingerprinting === -Peers may have different prune depths (depending on the peers configuration, disk space, etc.) which can result in a fingerprinting weakness (finding the prune depth through getdata requests). NODE_NETWORK_LIMITED supporting peers <I>SHOULD</I> avoid leaking the prune depth and therefore not serve blocks deeper then the signaled <code>NODE_NETWORK_LIMITED</code> thresholds. +Peers may have different prune depths (depending on the peers configuration, disk space, etc.) which can result in a fingerprinting weakness (finding the prune depth through getdata requests). NODE_NETWORK_LIMITED supporting peers <I>SHOULD</I> avoid leaking the prune depth and therefore not serve blocks deeper than the signaled <code>NODE_NETWORK_LIMITED</code> threshold (244 blocks). === Risks === |