joshua/dash-docs
1
0
Fork 0
mirror of https://github.com/seigler/dash-docs synced 2025-07-27 17:56:16 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

full-node: Add info on pruning to reduce storage

Browse source
This commit is contained in:
Will Binns 2017-01-01 17:41:06 -06:00
parent 0cb1412781
commit 54422ffcbf
1 changed files with 19 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

19
en/full-node.md
View file

@ -1287,6 +1287,25 @@ If you have any questions about configuring Bitcoin Core, please stop by
one of our [forums](/en/bitcoin-core/help#forums) or [live one of our [forums](/en/bitcoin-core/help#forums) or [live
chatrooms](/en/bitcoin-core/help#live). chatrooms](/en/bitcoin-core/help#live).
### Reduce Storage
It is possible to configure your node to to run in pruned mode in order to
reduce storage requirements. This can reduce the disk usage from over 100GB to
around 2GB.
Running a node in pruned mode disables the RPCs `importwallet`, `importaddress`,
and `importprivkey`.
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 because stored
blocks could be served to other nodes.
### Reduce Traffic ### Reduce Traffic
Some node operators need to deal with bandwith caps imposed by their ISPs. Some node operators need to deal with bandwith caps imposed by their ISPs.