feat: note on DA, DAS, erasure codes #135
Conversation
|
|
||
| A core responsibility of any layer-1 blockchain is to guarantee _data availability_. | ||
|
|
||
| Data availability refers to the availability of transactions in a block that is appended to the tip of the chain. During consensus, validators download the block to verify its availability. If the block contains any transactions that are withheld by a validator, the block is unavailable and will be rejected as invalid. |
There was a problem hiding this comment.
I would make it clear that DA is a prerequisite to validating the chain. It's not about data being available but being able to verify them with protocol rules
There was a problem hiding this comment.
Do you suggest I collate the exact rules that are being verified?
There was a problem hiding this comment.
No need to go to details. Just to point out that a node needs to verify transactions and validate blocks to be able to operate trustlessly and build the state which requires historical and latest data.
|
|
||
| In case (1), the block is valid and the light client can accept it. In case (2), it is expected that some other node will quickly construct and relay a fraud proof. In case (3), it is also expected that some other node will quickly construct and relay a specialized kind of fraud proof that shows that the erasure code is constructed incorrectly. If a light client receives no fraud proofs for some time, it will take that as evidence that the block is in fact valid. | ||
|
|
||
| An interesting implementation to study can be found [here](https://github.com/ethereum/research/tree/master/erasure_code/ec65536). |
There was a problem hiding this comment.
Please add a section for resources. There are many great articles on DA and solutions you explained here. Ethorg does a great job on DA https://ethereum.org/en/developers/docs/data-availability/
There was a problem hiding this comment.
Added a few interesting ones, lmk what you think!
|
took your suggestion and added it in verbatim 😅 @taxmeifyoucan |
There was a problem hiding this comment.
Thanks @ultraviolet10! One paragraph I would find missing is the changes to L2 data availability with introduction of ephemeral blobs
Got it, I'll add this in the next update. Thanks :) |
Adds compiled notes on data availability, sampling, and the concept of erasure codes.