-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add EIP: eth/70 - Sharded Blocks Protocol #9004
Conversation
✅ All reviewers have approved. |
The commit b994f42 (as a parent of 291af95) contains errors. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall I like this simple approach.
One downside to this approach i see, is that it will be harder to setup full sync nodes in remote geolocations, since a minimum number of peers is required, which might be difficult if ping is high.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All Reviewers Have Approved; Performing Automatic Merge...
This EIP introduces a method enabling an Ethereum node to communicate its available block spans via a bitlist, where each bit represents a 1-million-block span. Nodes use this bitlist to signal which spans of historical data they store, enabling peers to make informed decisions about data availability when requesting blocks. This aims to improve network efficiency by providing a probabilistic snapshot of data locality across nodes.
The proposal extends the Ethereum wire protocol (eth) with version eth/70, introducing a blockBitlist field in the handshake. Nodes probabilistically retain certain block spans to support data locality across the network.