highperfocused/bips
1
0
Fork 0
mirror of https://github.com/bitcoin/bips.git synced 2025-03-17 13:22:51 +01:00
Code Issues Packages Projects Releases Wiki Activity

BIP159: editorial fixups

Browse Source
This commit is contained in:
Jon Atack 2025-02-14 14:39:44 -06:00
parent 8118a14dc8
commit 5b85dbe120
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
bip-0159.mediawiki
View File

@ -13,15 +13,15 @@
== Abstract ==
Define a service bit that allow pruned peers to signal their limited services
Define a service bit that allows pruned peers to signal their limited services.
==Motivation==
Pruned peers can offer the same services as traditional peer except of serving all historical blocks.
Bitcoin right now only offers the NODE_NETWORK service bit which indicates that a peer can serve
Pruned peers can offer the same services as traditional peers, except that of serving all historical blocks.
Bitcoin right now only offers the <code>NODE_NETWORK</code> service bit to indicate that a peer can serve
all historical blocks.
# Pruned peers can relay blocks, headers, transactions, and addresses, but they only guarantee serving a minimum number of historical blocks; thus, they should have a way to announce their service(s)
# Peers no longer in initial block download should consider connecting some of its outbound connections to pruned peers to allow other peers to bootstrap from non-pruned peers
# Peers no longer in initial block download should consider connecting some of their outbound connections to pruned peers, to allow other peers to bootstrap from non-pruned peers
== Specification ==
@ -44,7 +44,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).
Peers may have different prune depths (depending on their configuration, disk space, etc.), which can result in a fingerprinting weakness (finding the prune depth through getdata requests).
Pruned nodes should therefore avoid leaking the prune depth and <I>SHOULD NOT</I> serve blocks deeper than the signaled <code>NODE_NETWORK_LIMITED</code> threshold of 288 blocks.