mirror of
https://github.com/monero-project/monero-site.git
synced 2024-12-15 04:46:35 +02:00
commit
a2c69f76ce
@ -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.
|
||||
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."
|
||||
qblocksize: How big is the Monero blockchain?
|
||||
ablocksize: "The Monero @blockchain is always growing so there is no fixed size. As of 2021, the full blockchain is around 95-100GB. A pruned blockchain is about 30GB. Check out Moneropedia entry @pruning to learn the difference between a full and a pruned blockchain."
|
||||
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."
|
||||
qavoidbc: Can I avoid downloading the entire blockchain?
|
||||
|
@ -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-long-sync">{% t faq.q5 %}</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-avoid-bc">{% t faq.qavoidbc %}</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>
|
||||
</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">
|
||||
<h3><a class="anchor" href="#anchor-block-space"></a>{% t faq.qblockspace %}</h3>
|
||||
<div class="tab-answer">
|
||||
|
Loading…
Reference in New Issue
Block a user