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 | Fraud and Data Availability Proofs |
|---|---|
| What the text proposes | Light clients can refuse a block if a fraud proof shows it is invalid, but only if the block's data was actually published. The paper shows how erasure coding and sampling let clients check publication without downloading everything. |
| Who may write | Mustafa Al-Bassam, Alberto Sonnino and Vitalik Buterin |
| What is settled | Encode the block so that any large enough sample reconstructs it. |
| Load-bearing assumption | This is the root of data-availability sampling, not a specification of Celestia, Ethereum danksharding, or any current parameter set. |
| What this library says afterwards | Samples do not tell you the state root was computed correctly unless a fraud proof or a validity proof is attached. |
| Rights | Official external source only |