Hacker News Reader

Comment by shazow | Hacker News Reader

Ethereum has a different blockchain design and ledger security properties than Bitcoin, an archival node is not required for a similar level of security (and is quite extraneous).

From Vitalik, on the link you shared:

> That chart is highly misleading. 300 GB is the size of a full archive node, which stores the history, present state and all historical states. The state itself is only ~1-2 GB and the history is ~10 GB. A pruned node would still store the full state and history, and so would be able to recompute any historical state if you really needed it, but it would only consume around 20 GB. If you only care about present state, you can go much lower.

https://www.reddit.com/r/ethereum/comments/6zcoja/10_gb_in_2...

More interesting details in this subthread: https://www.reddit.com/r/ethereum/comments/6zcoja/10_gb_in_2...

View on HN

>Ethereum has a different blockchain design and ledger security properties than Bitcoin, an archival node is not required for a similar level of security (and is quite extraneous).

doesn't bitcoin also have a feature similar to this? except bitcoin's pruned node takes ~3GB rather than etherum's 20GB.

> doesn't bitcoin also have a feature similar to this? except bitcoin's pruned node takes ~3GB rather than etherum's 20GB.

No, not in the same way. A pruned Bitcoin node loses validation/state that you can't reconstruct, it does not have the same security properties. See the links in my comment.

Yes, it is in the same way. In both cases you keep enough state to verify future transactions but not enough to rebuild up to the current state if it were to get corrupted. I don't see anything in your links that says otherwise.

The difference is that it's possible for new Etherium nodes to sync up using just the current state without having to trust the node they got it from or process the history, whereas new Bitcoin nodes have to either process the entire transaction history themselves or trust someone to give them a valid state copy. Also, pruned Bitcoin nodes are more analogous to Etherium nodes which only store the current state without any history (~1GB according to that link). I think the pruned nodes vbuterin talks about are roughly equivalent to unpruned Bitcoin nodes.

Nope, Ethereum fast sync has to trust that peers don't give it an invalid state (it checks that all it's peers have the same state, but that is much weaker protection). https://github.com/ethereum/go-ethereum/pull/1889

A 25 GB pruned Ethereum node is the same as a Bitcoin full node. A pruned Ethereum node is one that has pruned all intermediate states (the state refers to all account balances at a given block), which Bitcoin full nodes don't store (Bitcoin full nodes only keep a copy of the latest block's state, Ethereum full nodes keep a copy of every block's state).

So a pruned Ethereum node and a Bitcoin full node both have the entire transaction history and the current state.

Reply on news.ycombinator.com