diff options
| author | Luxter77 <Luxter77@users.noreply.github.com> | 2021-03-04 09:49:10 -0300 |
|---|---|---|
| committer | Luxter77 <Luxter77@users.noreply.github.com> | 2021-03-04 09:49:10 -0300 |
| commit | b3238a884d97ea977c069778eeb272650a300f9d (patch) | |
| tree | 0559cbe168d790ec6edb1ff7289db9543fb08db5 | |
| parent | Make pruning section more consistent in README.md (diff) | |
| download | monero-b3238a884d97ea977c069778eeb272650a300f9d.tar.xz | |
Update size figures on the pruning section of README.md
| -rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -704,7 +704,7 @@ DNS_PUBLIC=tcp torsocks ./monerod --p2p-bind-ip 127.0.0.1 --no-igd --rpc-bind-ip ## 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. +As of May 2020, the full Monero blockchain file is about 100 GB. One can store a pruned blockchain, which is about 30 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 |