aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorxor-freenet <xor@freenetproject.org>2016-01-27 15:53:40 +0100
committerxor-freenet <xor@freenetproject.org>2016-01-27 15:54:56 +0100
commit54d390780feaef895fede8da3f436b932af29c1d (patch)
treea415481f98f901bd4efcc7c2fec5b72d95a439ae
parenta683d20d5f88f0685cdacdcba928d6ec572390dd (diff)
downloadbitcoin-54d390780feaef895fede8da3f436b932af29c1d.tar.xz
doc: Fix wrong claims about blockchain reorganization with pruning
-rw-r--r--doc/release-notes.md11
1 files changed, 8 insertions, 3 deletions
diff --git a/doc/release-notes.md b/doc/release-notes.md
index 7049bd6c18..c22b4e760e 100644
--- a/doc/release-notes.md
+++ b/doc/release-notes.md
@@ -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
------------------------