monero-project/monero-site
monero-project/monero-site
1
0
Fork 0
mirror of https://github.com/monero-project/monero-site.git synced 2024-11-16 15:58:16 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Added FAQ 'How Big is the Monero blockchain?'

Browse source
This commit is contained in:
Tony 2021-01-28 11:06:40 -06:00
parent dcb4d97a92
commit 6d3d3c766a
2 changed files with 9 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
_i18n/en.yml
View file

@ -430,6 +430,8 @@ faq:
anodetor: Support for Tor is still in its infancies, but it's already possible to natively send transactions through the network and to run a Monero @daemon on the Tor network. Better Tor and I2P integrations are in progress. anodetor: Support for Tor is still in its infancies, but it's already possible to natively send transactions through the network and to run a Monero @daemon on the Tor network. Better Tor and I2P integrations are in progress.
qfullpruned: How do I decide if I should run a full node or a pruned node? qfullpruned: How do I decide if I should run a full node or a pruned node?
afullpruned: "A full @node requires a considerable amount of storage and could take a long time to download and verify the entire blockchain, especially on older hardware. If you have limited storage, a pruned node is recommended. It only stores 1/8th of unnecessary blockchain data while keeping the full transaction history. If plenty of storage is available, a full node is recommended but a pruned node still greatly contributes to the network and improves your privacy." afullpruned: "A full @node requires a considerable amount of storage and could take a long time to download and verify the entire blockchain, especially on older hardware. If you have limited storage, a pruned node is recommended. It only stores 1/8th of unnecessary blockchain data while keeping the full transaction history. If plenty of storage is available, a full node is recommended but a pruned node still greatly contributes to the network and improves your privacy."
qblocksize: How big is the Monero blockchain?
ablocksize: "The Monero @blockchain is always growing so there is no fixed size. As of 2021, the blockchain is around 95-100GB. "
qblockspace: Why does the blockchain need so much space? qblockspace: Why does the blockchain need so much space?
ablockspace: "When you download the @blockchain, you are downloading the entire history of the @transactions that happened in the Monero network since it was created. The transactions and the related data are heavy and the entire history must be kept by every node to ensure it's the same for everybody. @pruning a blockchain allows to run a node which keeps only 1/8 of not strictly necessary blockchain data. This results in a blockchain 2/3 smaller than a full one. Convenient for people with limited disk space. Check out the Moneropedia entries @node and @remote-node for more details." ablockspace: "When you download the @blockchain, you are downloading the entire history of the @transactions that happened in the Monero network since it was created. The transactions and the related data are heavy and the entire history must be kept by every node to ensure it's the same for everybody. @pruning a blockchain allows to run a node which keeps only 1/8 of not strictly necessary blockchain data. This results in a blockchain 2/3 smaller than a full one. Convenient for people with limited disk space. Check out the Moneropedia entries @node and @remote-node for more details."
qavoidbc: Can I avoid downloading the entire blockchain? qavoidbc: Can I avoid downloading the entire blockchain?

7
get-started/faq/index.md
View file

@ -50,6 +50,7 @@ permalink: /get-started/faq/index.html
<li><a href="#anchor-tor-node">{% t faq.qnodetor %}</a></li> <li><a href="#anchor-tor-node">{% t faq.qnodetor %}</a></li>
<li><a href="#anchor-long-sync">{% t faq.q5 %}</a></li> <li><a href="#anchor-long-sync">{% t faq.q5 %}</a></li>
<li><a href="#anchor-full-pruned">{% t faq.qfullpruned %}</a></li> <li><a href="#anchor-full-pruned">{% t faq.qfullpruned %}</a></li>
<li><a href="#anchor-block-size">{% t faq.qblocksize %}</a></li>
<li><a href="#anchor-block-space">{% t faq.qblockspace %}</a></li> <li><a href="#anchor-block-space">{% t faq.qblockspace %}</a></li>
<li><a href="#anchor-avoid-bc">{% t faq.qavoidbc %}</a></li> <li><a href="#anchor-avoid-bc">{% t faq.qavoidbc %}</a></li>
<li><a href="#anchor-scanned-wallet">{% t faq.qscanned %}</a></li> <li><a href="#anchor-scanned-wallet">{% t faq.qscanned %}</a></li>
@ -270,6 +271,12 @@ permalink: /get-started/faq/index.html
<p>{% t faq.afullpruned %}</p> <p>{% t faq.afullpruned %}</p>
</div> </div>
</div> </div>
<div class="tab" id="anchor-block-size">
<h3><a class="anchor" href="#anchor-block-size"></a>{% t faq.qblocksize %}</h3>
<div class="tab-answer">
<p>{% t faq.ablocksize %}</p>
</div>
</div>
<div class="tab" id="anchor-block-space"> <div class="tab" id="anchor-block-space">
<h3><a class="anchor" href="#anchor-block-space"></a>{% t faq.qblockspace %}</h3> <h3><a class="anchor" href="#anchor-block-space"></a>{% t faq.qblockspace %}</h3>
<div class="tab-answer"> <div class="tab-answer">