From fa810b3bff542200c50c4fd33fcfd982142b63ed Mon Sep 17 00:00:00 2001 From: MarcoFalke Date: Tue, 19 Dec 2017 13:52:46 -0500 Subject: [PATCH] bip159: Clarify that there is only one threshold --- bip-0159.mediawiki | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/bip-0159.mediawiki b/bip-0159.mediawiki index 79fd0fcf..9c880ed8 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 MUST 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 MUST be capable of serving at least the last 288 blocks (~2 days). |} -A safety buffer of additional 144 blocks to handle chain reorganizations SHOULD be taken into account when connecting to a peer signaling the NODE_NETWORK_LIMITED service bit. +A safety buffer of 144 blocks to handle chain reorganizations SHOULD be taken into account when connecting to a peer signaling the NODE_NETWORK_LIMITED service bit. === Address relay === @@ -42,7 +42,7 @@ Full nodes following this BIP SHOULD relay address/services (addrSHOULD avoid leaking the prune depth and therefore not serve blocks deeper then the signaled NODE_NETWORK_LIMITED 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 SHOULD avoid leaking the prune depth and therefore not serve blocks deeper than the signaled NODE_NETWORK_LIMITED threshold (244 blocks). === Risks ===