diff options
Diffstat (limited to 'bip-0157.mediawiki')
-rw-r--r-- | bip-0157.mediawiki | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/bip-0157.mediawiki b/bip-0157.mediawiki index 4a47706..d641a8e 100644 --- a/bip-0157.mediawiki +++ b/bip-0157.mediawiki @@ -168,7 +168,7 @@ fields: # Nodes SHOULD NOT send <code>getcfilters</code> unless the peer has signaled support for this filter type. Nodes receiving <code>getcfilters</code> with an unsupported filter type SHOULD NOT respond. # StopHash MUST be known to belong to a block accepted by the receiving peer. This is the case if the peer had previously sent a <code>headers</code> or <code>inv</code> message with that block or any descendents. A node that receives <code>getcfilters</code> with an unknown StopHash SHOULD NOT respond. -# The height of the block with hash StopHash MUST be greater than or equal to StartHeight, and the difference MUST be strictly less than 100. +# The height of the block with hash StopHash MUST be greater than or equal to StartHeight, and the difference MUST be strictly less than 1000. # The receiving node MUST respond to valid requests by sending one <code>cfilter</code> message for each block in the requested range, sequentially in order by block height. ==== cfilter ==== @@ -431,9 +431,9 @@ document proposes a solution purely at the P2P layer. The constant interval of 1,000 blocks between checkpoints was chosen so that, given the current chain height and rate of growth, the size of a -<code>cfcheckpt</code> message is not drastically from a -<code>cfheaders</code> between two checkpoints. Also, 1,000 is a nice round -number, at least to those of us who think in decimal. +<code>cfcheckpt</code> message is not drastically different from a +<code>cfheaders</code> message between two checkpoints. Also, 1,000 is a nice +round number, at least to those of us who think in decimal. == Compatibility == |