The Ethereum-blockchain size has exceeded 1TB, and yes, it’s an issue
This is not about archival nodes. This is about about staying in sync, after the fact. My Argument: Ethereum’s runaway data directory size is just the tip.
My Prediction: It will all work, until it doesn’t. My Suggestion: Transpose. My Argument: Ethereum’s runaway data directory size is just the tip.
My Prediction: It will all work, until it doesn’t. My Suggestion: Transpose. My Argument:
Larger blocks centralize validators. It’s that simple. It’s the central argument in the entire cryptocurrency community in regards to scaling.
Not many people familiar with blockchain protocol actually deny this. The following is an excerpt from what I consider to be a very well put together explanation of various “Layer 2” scaling options. (Of which, the only working one is already implemented on Bitcoin.)
The problem? Putting everything about Proof of Stake completely to the side, the incentive structure of the base layer is completely broken because there is no cap on Ethereum’s blocksize, and even if one was put in place it would have to be reasonable, and then these Dapps wouldn’t even work because they’re barely working now with no cap. It doesn’t even matter what that cap is set at for this argument to hold because right now there is none in place.