diff options
| author | moneromooo-monero <moneromooo-monero@users.noreply.github.com> | 2020-05-31 22:18:14 +0000 |
|---|---|---|
| committer | moneromooo-monero <moneromooo-monero@users.noreply.github.com> | 2020-06-01 17:48:11 +0000 |
| commit | b6e904e547d008aee6b433489c86a4d8db13cd3f (patch) | |
| tree | 7bb9fba2a227f07d85e4ed407b5d80b232fca995 /README.md | |
| parent | Merge pull request #6582 (diff) | |
| download | monero-b6e904e547d008aee6b433489c86a4d8db13cd3f.tar.xz | |
README: mention pruning
Diffstat (limited to '')
| -rw-r--r-- | README.md | 11 |
1 files changed, 11 insertions, 0 deletions
@@ -22,6 +22,7 @@ Portions Copyright (c) 2012-2013 The Cryptonote developers. - [Dependencies](#dependencies) - [Internationalization](#Internationalization) - [Using Tor](#using-tor) + - [Pruning](#Pruning) - [Debugging](#Debugging) - [Known issues](#known-issues) @@ -671,6 +672,16 @@ DNS_PUBLIC=tcp torsocks ./monerod --p2p-bind-ip 127.0.0.1 --no-igd --rpc-bind-ip --data-dir /home/amnesia/Persistent/your/directory/to/the/blockchain ``` +## Pruning + +As of May 2020, the full Monero blockchain file is about 80 GB. One can store a pruned blockchain, which is about 28 GB. +A pruned blockchain can only serve part of the historical chain data to other peers, but is otherwise identical in +functionality to the full blockchain. +To use a pruned blockchain, it is best to start the initial sync with --prune-blockchain. However, it is also possible +to prune an existing blockchain using the monero-blockchain-prune tool or using the --prune-blockchain monerod option +with an existing chain. If an existing chain exists, pruning will temporarily require disk space to store both the full +and pruned blockchains. + ## Debugging This section contains general instructions for debugging failed installs or problems encountered with Monero. First, ensure you are running the latest version built from the Github repo. |