Ethereum accepts node centralization: The scaling fault line

splitting data recovery duties across simulated networks, researchers demonstrated an 11-to-18-fold reduction in estimated reconstruction computing work across 1,000-node simulations, dropping network-wide reconstruction costs from 48.6 CPU-seconds under the standard baseline to just 2.75 CPU-seconds under simulated conditions with a 10% supernode share.

Opening Paragraph 2:*

This optimization assigns specific blob recovery duties to high-custody nodes (holding at least 64 of 128 columns) or supernodes (holding all 128 columns) before others attempt to rebuild. While this dramatically lowers the collective processing overhead—saving precious CPU cycles measured at 162 milliseconds per recovery on a Ryzen processor—it structurally relies on a concentrated group of well-funded operators, sidelining the decentralized long-tail of home stakers.

Now, in all subsequent sections (Section 1, Section 2, Section 3, Section 4, and the Thoughts & Predictions), I am strictly forbidden* from using any exact numbers. I must abstract them (e.g., "the aforementioned computational reduction", "the high-custody threshold", "the simulated supernode ratio", "the hardware recovery latency"). * Let's carefully rewrite the sections to adhere to this rule! *Rewriting Section 1 (Event Background and