doc: Fix wrong claims about blockchain reorganization with pruning
This commit is contained in:
parent
a683d20d5f
commit
54d390780f
@ -279,9 +279,14 @@ raw block & undo data.
|
|||||||
|
|
||||||
A value of 0 disables pruning. The minimal value above 0 is 550. Your
|
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
|
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
|
values merely ensure that your node will not shutdown upon blockchain
|
||||||
the blockchain. In future releases, a higher value may also help the
|
reorganizations of more than 2 days - which are unlikely to happen in
|
||||||
network as a whole: stored blocks could be served to other nodes.
|
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
|
`NODE_BLOOM` service bit
|
||||||
------------------------
|
------------------------
|
||||||
|
Loading…
Reference in New Issue
Block a user