From cf9661509eb20a6470935f49a02a78360ec087bb Mon Sep 17 00:00:00 2001 From: Lucas Daniel Velazquez M <19197331+Luxter77@users.noreply.github.com> Date: Tue, 2 Mar 2021 15:11:40 -0300 Subject: [PATCH 1/3] Make pruning section more consistent in README.md use syntax highlighting on commands and command line arguments --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index a3cecb3b5..7718c3ea3 100644 --- a/README.md +++ b/README.md @@ -707,8 +707,8 @@ DNS_PUBLIC=tcp torsocks ./monerod --p2p-bind-ip 127.0.0.1 --no-igd --rpc-bind-ip 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 +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. From b3238a884d97ea977c069778eeb272650a300f9d Mon Sep 17 00:00:00 2001 From: Luxter77 Date: Thu, 4 Mar 2021 09:49:10 -0300 Subject: [PATCH 2/3] Update size figures on the pruning section of README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 7718c3ea3..7dad433e8 100644 --- a/README.md +++ b/README.md @@ -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 From bf86e9527fd32c05826bc0a8a30cc4d7c1555dc5 Mon Sep 17 00:00:00 2001 From: Luxter77 Date: Thu, 4 Mar 2021 09:49:52 -0300 Subject: [PATCH 3/3] added link to moneropedia to pruning in README.md --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index 7dad433e8..687ab40b4 100644 --- a/README.md +++ b/README.md @@ -712,6 +712,8 @@ to prune an existing blockchain using the `monero-blockchain-prune` tool or usin with an existing chain. If an existing chain exists, pruning will temporarily require disk space to store both the full and pruned blockchains. +For more detailed information see the ['Pruning' entry in the Moneropedia](https://www.getmonero.org/resources/moneropedia/pruning.html) + ## 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.