Add EIP: PeerDAS - Peer Data Availability Sampling #8105
Conversation
github-actions
bot
added
c-new
File
|
EIPS/peerdas.md
Outdated
|
|
||
| Nodes find and maintain a diverse peer set and sample columns from their peers to perform DAS. | ||
|
|
||
| A node can reconstruct the entire data matrix if it acquires over 50% of all the columns. If a node has less than 50%, it can request the necessary columns from the peer nodes. |
There was a problem hiding this comment.
>= 50%
| A node can reconstruct the entire data matrix if it acquires over 50% of all the columns. If a node has less than 50%, it can request the necessary columns from the peer nodes. | |
| A node can reconstruct the entire data matrix if it acquires at least 50% of all the columns. If a node has less than 50%, it can request the necessary columns from the peer nodes. |
EIPS/peerdas.md
Outdated
| @@ -0,0 +1,52 @@ | |||
| --- | |||
There was a problem hiding this comment.
| --- | |
| --- | |
| eip: 7594 |
Assigning next sequential EIP/ERC/RIP number.
Numbering changed to sequential from 7500 and is no longer the PR number.
Please also update the filename.
EIPS/peerdas.md
Outdated
|
|
||
| ## Specification | ||
|
|
||
| We extend the blobs introduced in EIP-4844 using a one-dimensional erasure coding extension. Each row consists of the blob data combined with its erasure code. It is subdivided into cells, which are the smallest units that can be authenticated with their KZG commitments. Each column, associated with a specific gossip subnet, consists of the cells from all rows for a specific index. Each node is responsible for maintaining and custodying a deterministic set of column subnets and data as a function of their node ID. |
There was a problem hiding this comment.
a diagram here would be very illustrative (just a suggestion, so if you already have one please patch it)
| --- | ||
| eip: 7594 | ||
| title: PeerDAS - Peer Data Availability Sampling | ||
| description: Introducing simple DAS utilizing gossip distribution and peer requests |
There was a problem hiding this comment.
| description: Introducing simple DAS utilizing gossip distribution and peer requests | |
| description: Introducing one dimensional DAS utilizing peer gossip, distribution and requests |
There was a problem hiding this comment.
allows to be more specific for this proposal and in future add a new EIPs for e.g. 2 dimensional peer das
| @@ -0,0 +1,52 @@ | |||
| --- | |||
| eip: 7594 | |||
| title: PeerDAS - Peer Data Availability Sampling | |||
There was a problem hiding this comment.
| title: PeerDAS - Peer Data Availability Sampling | |
| title: 1D-PeerDAS - Peer Data Availability Sampling |
|
|
||
| ## Abstract | ||
|
|
||
| PeerDAS (Peer Data Availability Sampling) is a networking protocol that allows beacon nodes to perform data availability sampling (DAS) to ensure that blob data has been made available while downloading only a subset of the data. PeerDAS utilizes gossip for distribution, discovery for finding peers of particular data custody, and peer requests for sampling. |
There was a problem hiding this comment.
| PeerDAS (Peer Data Availability Sampling) is a networking protocol that allows beacon nodes to perform data availability sampling (DAS) to ensure that blob data has been made available while downloading only a subset of the data. PeerDAS utilizes gossip for distribution, discovery for finding peers of particular data custody, and peer requests for sampling. | |
| PeerDAS (Peer Data Availability Sampling) is a networking protocol that allows beacon nodes to perform data availability sampling (DAS) to ensure that blob data has been made available while downloading only a subset of the data. PeerDAS utilizes gossip for distribution, discovery for finding peers of particular data custody, and peer requests for sampling. | |
| This particular proposal deals with one dimensional DAS |
|
@hwwhww if you can fix some references and make CI pass, i can probably approve this and get merged in draft status |
|
The commit ecdda9b (as a parent of 4b8d63d) contains errors. |
Co-authored-by: g11tech <[email protected]>
|
Hi @g11tech, thank you so much for your reviews and suggestions! It's better to merge it now and keep the title simple (no 1-D). We can make the new name more descriptive if there is new derivative. |
EIPs generally can't be edited once final so might not happen, however I am approving this , you can update it anytime before going to final if you would want to |
* Add EIP: PeerDAS - Peer Data Availability Sampling * Rename to EIP-7594 and apply PR suggestion * Add links * Update EIPS/eip-7594.md * Apply suggestions from code review Co-authored-by: g11tech <[email protected]> --------- Co-authored-by: g11tech <[email protected]>
* Add EIP: PeerDAS - Peer Data Availability Sampling * Rename to EIP-7594 and apply PR suggestion * Add links * Update EIPS/eip-7594.md * Apply suggestions from code review Co-authored-by: g11tech <[email protected]> --------- Co-authored-by: g11tech <[email protected]>
Add EIP: PeerDAS - Peer Data Availability Sampling draft to get an EIP number.
Once we get an EIP number, we will update the CL specs file path, and then add the circular link to the EIP content later.