From 4b6513db8e1448ccd2968a96a3b0b500aee3817f Mon Sep 17 00:00:00 2001 From: Justin Ehrenhofer Date: Thu, 31 Jan 2019 21:04:45 +0100 Subject: [PATCH] Update 2019-02-01-pruning.md --- _posts/2019-02-01-pruning.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_posts/2019-02-01-pruning.md b/_posts/2019-02-01-pruning.md index a2380047..49881a54 100644 --- a/_posts/2019-02-01-pruning.md +++ b/_posts/2019-02-01-pruning.md @@ -14,7 +14,7 @@ Pruning is the process of removing non-critical blockchain information from loca For Bitcoin, many people discuss pruning in the context of intermediary transactions. For example, suppose Alice sends Bob 1 BTC, and then Bob sends this to Charlie. The blockchain would record records of transactions A -> B and B -> C. However, since Alice can no longer spend her funds, it's less important to retain this information. Therefore, nodes can prune this information with a relatively high level of safety. Other nodes on the network would step in if something malicious occurs. -This above example does not apply to Monero, since we do not know when money is spent. However, Monero nodes can prune a lot of other unnecessary information. This includes ring signature data that isn't essential to prevent double-spends. While the Monero blockchain can theoretically be pruned far further than this release enables, more testing is needed to test these limits. +This above example does not apply to Monero, since we do not know when money is spent. However, Monero nodes can prune a lot of other unnecessary information. This includes ring signature data that isn't essential to prevent double-spends. While the Monero blockchain can theoretically be pruned far further than this release enables, more testing is needed to push these limits. ### Pruning Savings