Compare
Four documents, the same five questions.
No throughput league table and no yield. The cells are what this library is willing to say about the text.
| Question | Shard Blob Transactions |
|---|---|
| What the text proposes | A new transaction type carries a blob: a large chunk of data that consensus nodes hold briefly and that the execution layer cannot read byte by byte. Rollups are the intended user. The blob is not cheap forever, and it is not the rollup's proof. |
| Who may write | Vitalik Buterin, Dankrad Feist, Diederik Loerakker, George Kadianakis, Matt Garnett, Mofi Taiwo and Ansgar Dietrichs |
| What is settled | A blob-carrying transaction commits to blobs with a KZG commitment. |
| Load-bearing assumption | A blob is not a validity proof. An optimistic rollup still has a challenge. A zk rollup still needs a proof. |
| What this library says afterwards | Data that expires cannot later be fetched from Ethereum itself. Someone else must have kept a copy if it is still needed. |
| Rights | Official external source only |