mirror of
https://github.com/seigler/dash-docs
synced 2025-07-27 09:46:12 +00:00
full-node: Add info on pruning to reduce storage
This commit is contained in:
parent
0cb1412781
commit
54422ffcbf
1 changed files with 19 additions and 0 deletions
|
@ -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
|
||||
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
|
||||
|
||||
Some node operators need to deal with bandwith caps imposed by their ISPs.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue