doc: Fix wrong claims about blockchain reorganization with pruning

This commit is contained in:
xor-freenet 2016-01-27 15:53:40 +01:00
parent a683d20d5f
commit 54d390780f
No known key found for this signature in database
GPG Key ID: CB6667EF2D8D6B79
1 changed files with 8 additions and 3 deletions

View File

@ -279,9 +279,14 @@ raw block & undo data.
A value of 0 disables pruning. The minimal value above 0 is 550. Your
wallet is as secure with high values as it is with low ones. Higher
values merely reduce the network traffic in case of reorganization of
the blockchain. In future releases, a higher value may also help the
network as a whole: stored blocks could be served to other nodes.
values merely ensure that your node will not shutdown upon blockchain
reorganizations of more than 2 days - which are unlikely to happen in
practice unless there is a hard fork. In future releases, a higher value
may also help the network as a whole: stored blocks could be served to
other nodes.
For further information about pruning, you may also consult the [release
notes of v0.11.0](https://github.com/bitcoin/bitcoin/blob/v0.11.0/doc/release-notes.md#block-file-pruning).
`NODE_BLOOM` service bit
------------------------