aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorxor-freenet <xor@freenetproject.org>2016-01-25 18:07:33 +0100
committerxor-freenet <xor@freenetproject.org>2016-01-25 18:23:06 +0100
commitfe074ccb3798b0c7c8ddc221342eb3cfb593f168 (patch)
tree9f96513e2540920e0f541ec13e20326ae503199d
parent7c5e90e8dde30d9f42a0a1e9a6a0fbba8bce2c79 (diff)
downloadbitcoin-fe074ccb3798b0c7c8ddc221342eb3cfb593f168.tar.xz
doc: Explain effects of -prune=<n> parameter in release notes
As discussed in the mailing list thread: [bitcoin-dev] Bitcoin Core 0.12.0 release candidate 1 available in the replies to this message: http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2016-January/012276.html Please review thoroughly, I'm a newbie.
-rw-r--r--doc/release-notes.md11
1 files changed, 11 insertions, 0 deletions
diff --git a/doc/release-notes.md b/doc/release-notes.md
index 3f1e578763..452e2dcbfc 100644
--- a/doc/release-notes.md
+++ b/doc/release-notes.md
@@ -267,6 +267,9 @@ Wallet: Pruning
---------------
With 0.12 it is possible to use wallet functionality in pruned mode.
+This can reduce the disk usage from currently around 60 GB to
+less than 1 GB.
+
However, rescans as well as the RPCs `importwallet`, `importaddress`,
`importprivkey` are disabled.
@@ -274,6 +277,14 @@ To enable block pruning set `prune=<N>` on the command line or in
`bitcoin.conf`, where `N` is the number of MiB to allot for
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: The stored blocks could be served to other nodes.
+Currently, nodes with pruning enabled do not serve block data at all
+and thus could be considered as "leechers".
+
`NODE_BLOOM` service bit
------------------------