diff options
| author | Alexander Blair <snipa@jagtech.io> | 2020-08-26 12:53:54 -0700 |
|---|---|---|
| committer | Alexander Blair <snipa@jagtech.io> | 2020-08-26 12:53:55 -0700 |
| commit | aadd72202f9d43cdbe9b79f4eef2d44a3c9e2971 (patch) | |
| tree | 2cabf5c3af2faecbd4fcb188b0fbc5c86838b7e2 | |
| parent | Merge pull request #6607 (diff) | |
| parent | README: mention pruning (diff) | |
| download | monero-aadd72202f9d43cdbe9b79f4eef2d44a3c9e2971.tar.xz | |
Merge pull request #6610
b6e904e54 README: mention pruning (moneromooo-monero)
| -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) @@ -679,6 +680,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. |