diff options
| author | Lucas Daniel Velazquez M <19197331+Luxter77@users.noreply.github.com> | 2021-03-02 15:11:40 -0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-03-02 15:11:40 -0300 |
| commit | cf9661509eb20a6470935f49a02a78360ec087bb (patch) | |
| tree | b92a4ad610d6029ee0a4f63c1a9ffa4260173849 /README.md | |
| parent | Merge pull request #7381 (diff) | |
| download | monero-cf9661509eb20a6470935f49a02a78360ec087bb.tar.xz | |
Make pruning section more consistent in README.md
use syntax highlighting on commands and command line arguments
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -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. |