Trying to summarize: the size of blockchain data on Ethereum doesn't tell you about the disk space you need to efficiently validate Ethereum transactions because Ethereum's head state (43% additional space you need in addition to blockchain size) is very complicated relative to Bitcoin's "head state" (the UTXO set, 1.2%). The head state is the result of running all the txs which you need to validate future txs.
I'm still not sure how Ehereum "prunes" this state to be the 130GB that it is normally ... given that an archival node requires so much more state, 9GB. How is it determining which state is irrelevant?
reply