diff options
| author | Wladimir J. van der Laan <laanwj@gmail.com> | 2016-01-27 17:08:52 +0100 |
|---|---|---|
| committer | Wladimir J. van der Laan <laanwj@gmail.com> | 2016-01-27 17:09:41 +0100 |
| commit | 32e3538752f99a48ede99382505b07cec97da212 (patch) | |
| tree | e27c69070a52a4234244d6ab79a7915e037a4f27 /doc/release-notes.md | |
| parent | 38bf790d70b5eba2d3280f8c4809b15d386e3433 (diff) | |
| parent | 8c5f90306c12142586024023785f20cac7b22055 (diff) | |
Merge #7416: doc: Explain effects of -prune=<n> parameter in release notes
8c5f903 doc: In release notes, reduce length of pruning section (xor-freenet)
15c0263 doc: Minor spelling fix (xor-freenet)
54d3907 doc: Fix wrong claims about blockchain reorganization with pruning (xor-freenet)
a683d20 doc: Minor sentence length / capitalization fixes (xor-freenet)
58e3abf doc: In release notes, increase estimate of disk usage with pruning (xor-freenet)
be4b474 doc: In release notes, do not claim that pruning is leeching (xor-freenet)
46d7eb6 doc: Fix minimal disk usage with pruning enabled (xor-freenet)
fe074cc doc: Explain effects of -prune=<n> parameter in release notes (xor-freenet)
Diffstat (limited to 'doc/release-notes.md')
| -rw-r--r-- | doc/release-notes.md | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/doc/release-notes.md b/doc/release-notes.md index e862793dd9..661f943d76 100644 --- a/doc/release-notes.md +++ b/doc/release-notes.md @@ -290,6 +290,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 +around 2 GB. + However, rescans as well as the RPCs `importwallet`, `importaddress`, `importprivkey` are disabled. @@ -297,6 +300,16 @@ 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 ensure that your node will not shut down upon blockchain +reorganizations of more than 2 days - which are unlikely to happen in +practice. 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 ------------------------ |