CryptoSlate
An Ethereum prototype that assigns blob-recovery duties to selected high-custody nodes cut estimated reconstruction work by 11–18× across 1,000-node simulations. With four blobs, 10% supernodes and no columns withheld, network-wide reconstruction cost fell from 48.6 CPU-seconds under PeerDAS to 2.75 CPU-seconds under the reduced design. At a 20% supernode share, the figures were 91 and 6.6 CPU-seconds.
The results come from a report by researcher Csaba Kiraly. They describe accumulated computing work across the simulated network, not elapsed recovery time, using a measured 162-millisecond cost per blob recovery on a Ryzen 9 8945HS processor.
Why it matters
Ethereum’s blobs carry data used by layer-2 rollups, while PeerDAS allows nodes to verify data availability by downloading only part of it. High-custody nodes must hold at least 64 of 128 data columns, and supernodes hold all 128. When many nodes reconstruct the same missing blob, the network can repeat expensive work.
The reduced design assigns particular blobs to designated nodes first. Other nodes can receive recovered data through existing column-distribution channels instead of immediately rebuilding it, while high-custody nodes retain a delayed recovery role for anything still missing.
The approach is narrower than full RowDAS, which would add row channels so smaller nodes can pool data and reconstruct collectively. The prototype therefore reduces processor work without providing RowDAS’s additional resilience or changing blob limits.
Market impact
The main near-term benefit is lower reconstruction demand for operators serving Ethereum’s growing rollup ecosystem. That could reduce the computing burden on home stakers and other high-custody node operators as blob activity increases.
The findings are still limited to simulated, in-process networks using real cryptography. Larger simulations, devnet testing and the full 128-row-subnet configuration remain future work, so investors should treat the reported gains as an early design signal rather than a forecast of current network costs.
Frequently asked questions
-
How much reconstruction work did the reduced PeerDAS design save?
Across 1,000-node simulations, estimated reconstruction work fell by 11–18×. With 10% supernodes, cost dropped from 48.6 to 2.75 CPU-seconds.
-
Why does Ethereum assign blob-recovery duties to selected nodes?
The design lets designated high-custody nodes recover specific blobs first. Other nodes can then receive the recovered data instead of repeating the same work.
-
What is the difference between the reduced design and full RowDAS?
The reduced design uses existing column-distribution channels and retains a high-custody-node backstop. Full RowDAS would add row channels for collective reconstruction and greater resilience.
-
Does the prototype prove lower fees or faster Ethereum transactions?
No. The reported measurements covered network-wide reconstruction work, not transaction speed, fee savings or elapsed recovery time.
-
What tests are still needed before this Ethereum design can be adopted?
The results remain limited to simulated, in-process networks using real cryptography. Larger simulations, devnet testing and validation of the full 128-row-subnet configuration are still required.
WuBlockchain
CoinDesk
Crypto News
CoinTelegraph
Benjamin Cowen
Glassnode