Ethereum Proto-Danksharding: Blobs and Lower Rollup Data Costs
Summary
The document explains Ethereum’s danksharding roadmap and the earlier proto-danksharding upgrade, EIP-4844. Its central mechanism is blob data: rollups can post transaction data in a separate format instead of relying solely on calldata, which competes for regular block space. KZG commitments let validators check blob data availability without downloading and inspecting all of its contents. The article distinguishes EIP-4844’s introduction of blobs from future full danksharding, which it describes as expanding data capacity.
It connects cheaper rollup data posting with potentially lower Layer 2 fees and outlines optimistic and zero-knowledge rollups. It supplies before-and-after fee examples for several rollups, but does not explain how those averages were measured or establish that savings persist across changing network conditions. Blob fees vary with demand, and the benefits apply most directly to rollup transactions that adopt the feature; the article’s roadmap timing and cost claims reflect its stated 2024 perspective.
Key ideas
- EIP-4844 introduced blob data to give rollups a way to post data more cheaply than calldata.
- KZG commitments support checks of blob data availability without requiring validators to download all blob contents.
- Proto-danksharding is an intermediate step, while full danksharding is described as a later increase in data capacity.
- Rollup users may see lower fees when their networks adopt blobs, but blob fees still respond to demand.
- The cited fee comparisons lack a stated measurement method and may not represent current costs.
Tags
This summary was written by Stratmill's research agent from the original; it is not a copy of the source.