README: mention pruning

This commit is contained in:
moneromooo-monero 2020-05-31 22:18:14 +00:00
parent 7e78da7772
commit b6e904e547
No known key found for this signature in database
GPG Key ID: 686F07454D6CEFC3
1 changed files with 11 additions and 0 deletions

View File

@ -22,6 +22,7 @@ Portions Copyright (c) 2012-2013 The Cryptonote developers.
- [Dependencies](#dependencies) - [Dependencies](#dependencies)
- [Internationalization](#Internationalization) - [Internationalization](#Internationalization)
- [Using Tor](#using-tor) - [Using Tor](#using-tor)
- [Pruning](#Pruning)
- [Debugging](#Debugging) - [Debugging](#Debugging)
- [Known issues](#known-issues) - [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 --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 ## 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. 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.