<blockquote>
<p>When accountants calculate the current years income, they don't go back to when the company started and add up every income and expense item, they just add the current years results to the archived past totals. What am I missing.</p>
</blockquote>
<p>The accountants won't start from the beginning, because they will have <em>already</em> done all of those calculations in previous years. This is similar to the function of a bitcoin node: it will not recompute the whole history to validate each new block, it will just validate each block once, and then store the network state, so that it can validate future blocks against that state.</p>
<p>The bottom line is, if you want to independently validate the history of the network, then you need to start from the beginning. Any other method will involve trusting that someone has supplied you with a legitimate intermediate state for you to begin your calculations from.</p>
<p>Note that a full node validating the chain is different than a miner working on finding new blocks. When people talk about the energy use of the bitcoin network, they are usually referring to the energy consumed by miners, not nodes.</p>

CC BY-SA 4.0
2021-05-21T02:33:00.917Z
2021-05-21T03:07:06.230Z
2021-05-21T03:07:06.230Z
chytrik
<p>There is no difference between those two things. If you have a data set that includes only things that you have fully validated all of and you confirm that something is in that data set, you have fully validated all of it. So checking that it's in a data set of things you have validated cannot be done <em>instead of</em> validating the entire chain because it <em>does</em> validate the entire chain.</p>
<p>I'm not sure what you mean by &quot;archived to save energy&quot;. If they aren't archived, they're stored. If they are archived, they're stored. So I'm not sure how energy would be saved.</p>

CC BY-SA 4.0
2021-05-20T15:30:49.463Z
2021-05-20T15:30:49.463Z
David Schwartz
<p>Perhaps more a clarification than an answer: there is absolutely no need for validating nodes to keep a copy of the full historical blockchain around, and it's unnecessary to have access to the chain's data for validation. Storing the block data or not is pretty much irrelevant for energy usage.</p>
<p>In Bitcoin Core (a fully-validating node that's often considered a reference implementation), there is a possibility of running in &quot;pruned&quot; mode, where all blocks are downloaded and fully validated, one by one, but deleted from disk afterwards. This is possible because the full block data is actually not necessary for validating future full blocks; only the set of unspent transaction outputs created by that block need to be retained. This is done in a separate database that is only a few GB in size, compared to a few 100 GB for the full blockchain.</p>
<p>The only impact this pruning mode has is not being able to scan for historical transactions (e.g. you can't import an old wallet because it won't be able to find those old transactions), and being unable to provide the historical blockchain to new nodes that are still synchronizing (which they need, even if they'll eventually prune that data away too).</p>

CC BY-SA 4.0
2021-05-20T18:08:35.447Z
2021-05-20T21:42:19.383Z
2021-05-20T21:42:19.383Z
Pieter Wuille
<p>I'm new to this so don't laugh.  If all of the previous transactions in a blockchain have been validated as authentic, why does the entire chain have to be carried forward in the calculations?  Why can't the validated portions be hashed and archived to save energy costs from handling so much historical data.  When accountants calculate the current years income, they don't go back to when the company started and add up every income and expense item, they just add the current years results to the archived past totals.  What am I missing.</p>

<blockchain><validation><energy-consumption>
Why must the entire chain be included in calculations if it's already been validated. Why can't the validated portions be archived to save energy?
Ed Would
# Why must the entire chain be included in calculations if it's already been validated. Why can't the validated portions be archived to save energy?

(Asked by: username_0 on 2021-05-20)

I'm new to this so don't laugh. If all of the previous transactions in a blockchain have been validated as authentic, why does the entire chain have to be carried forward in the calculations? Why can't the validated portions be hashed and archived to save energy costs from handling so much historical data. When accountants calculate the current years income, they don't go back to when the company started and add up every income and expense item, they just add the current years results to the archived past totals. What am I missing.

**Tags:** blockchain, validation, energy-consumption


---

## 3 answers

### Answer by username_1 on 2021-05-21. Score: 1 | Accepted answer

> When accountants calculate the current years income, they don't go back to when the company started and add up every income and expense item, they just add the current years results to the archived past totals. What am I missing.

The accountants won't start from the beginning, because they will have *already* done all of those calculations in previous years. This is similar to the function of a bitcoin node: it will not recompute the whole history to validate each new block, it will just validate each block once, and then store the network state, so that it can validate future blocks against that state.

The bottom line is, if you want to independently validate the history of the network, then you need to start from the beginning. Any other method will involve trusting that someone has supplied you with a legitimate intermediate state for you to begin your calculations from.

Note that a full node validating the chain is different than a miner working on finding new blocks. When people talk about the energy use of the bitcoin network, they are usually referring to the energy consumed by miners, not nodes.


---

### Answer by username_2 on 2021-05-20. Score: 2

There is no difference between those two things. If you have a data set that includes only things that you have fully validated all of and you confirm that something is in that data set, you have fully validated all of it. So checking that it's in a data set of things you have validated cannot be done *instead of* validating the entire chain because it *does* validate the entire chain.

I'm not sure what you mean by "archived to save energy". If they aren't archived, they're stored. If they are archived, they're stored. So I'm not sure how energy username_0 be saved.


---

### Answer by username_3 on 2021-05-20. Score: 1

Perhaps more a clarification than an answer: there is absolutely no need for validating nodes to keep a copy of the full historical blockchain around, and it's unnecessary to have access to the chain's data for validation. Storing the block data or not is pretty much irrelevant for energy usage.

In Bitcoin Core (a fully-validating node that's often considered a reference implementation), there is a possibility of running in "pruned" mode, where all blocks are downloaded and fully validated, one by one, but deleted from disk afterwards. This is possible because the full block data is actually not necessary for validating future full blocks; only the set of unspent transaction outputs created by that block need to be retained. This is done in a separate database that is only a few GB in size, compared to a few 100 GB for the full blockchain.

The only impact this pruning mode has is not being able to scan for historical transactions (e.g. you can't import an old wallet because it won't be able to find those old transactions), and being unable to provide the historical blockchain to new nodes that are still synchronizing (which they need, even if they'll eventually prune that data away too).


---

