From 54d390780feaef895fede8da3f436b932af29c1d Mon Sep 17 00:00:00 2001 From: xor-freenet Date: Wed, 27 Jan 2016 15:53:40 +0100 Subject: [PATCH] doc: Fix wrong claims about blockchain reorganization with pruning --- doc/release-notes.md | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/doc/release-notes.md b/doc/release-notes.md index 7049bd6c1..c22b4e760 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 ------------------------