Ethereum may have a simpler way to ease the computing burden of its growing rollup ecosystem

An Ethereum prototype that divides blob-recovery duties among nodes reported an 11–18× reduction in estimated reconstruction computing work across 1,000-node simulations. The results suggest operators could reduce duplicated work through a smaller change than the full RowDAS networking proposal.Researcher Csaba Kiraly's Sept. 3 report describes the reduced design as a possible first step toward RowDAS. It assigns recovery duties without introducing the new row-networking channels in the full proposal.Blobs carry data used by layer-2 rollups. PeerDAS, Ethereum's system for checking that blob data is available, lets nodes download only part of it. High-custody nodes hold at least 64 of the 128 data columns, enough to rebuild missing blob data; supernodes hold all 128.Many high-custody nodes can repeat the same reconstruction. The reduced design assigns particular blobs to them first, allowing others to receive the recovered data instead of immediately rebuilding it themselves.What the Ethereum blob-recovery simulations showIn one configuration with four blobs, 10% supernodes and no columns withheld, the estimated network-wide reconstruction cost fell from 48.6 CPU-seconds under the P...