Add EIP: Reduced Attestation Format #8372
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
c-new
File
|
eth-bot
added
e-consensus
eth-bot
changed the title
|
The commit b33dc5d (as a parent of 62a74a1) contains errors. |
eth-bot
changed the title
abcoathup
reviewed
Apr 2, 2024
EIPS/eip-7610.md
Outdated
| @@ -0,0 +1,99 @@ | |||
| --- | |||
| eip: 7610 | |||
There was a problem hiding this comment.
Suggested change
| eip: 7610 | |
| eip: 7670 |
Assigning next sequential EIP/ERC/RIP number.
Numbering changed to sequential from 7500.
Please also update the filename.
abcoathup
reviewed
Apr 2, 2024
g11tech
reviewed
Apr 3, 2024
g11tech
reviewed
Apr 3, 2024
EIPS/eip-7610.md
Outdated
|
|
||
| ## Motivation | ||
|
|
||
| Attestations currently dominate the bandwidth usage of the Consensus Layer's gossip network (approx. 90% of the traffic). By optimizing the size of `AttestationData`, the aim is to reduce network load to improve node performance, and, most importantly, allow for greater throughput of other significant consensus data, such as Blobs. As a matter of fact, the current `Attestation` structure is not optimized for network transmission, leading to unnecessarily high bandwidth consumption. As a matter of fact, the application of Snappy block compression only reduces the size of an attestation by less than 10%. |
There was a problem hiding this comment.
Suggested change
| Attestations currently dominate the bandwidth usage of the Consensus Layer's gossip network (approx. 90% of the traffic). By optimizing the size of `AttestationData`, the aim is to reduce network load to improve node performance, and, most importantly, allow for greater throughput of other significant consensus data, such as Blobs. As a matter of fact, the current `Attestation` structure is not optimized for network transmission, leading to unnecessarily high bandwidth consumption. As a matter of fact, the application of Snappy block compression only reduces the size of an attestation by less than 10%. | |
| Attestations currently dominate the bandwidth usage of the Consensus Layer's gossip network (approx. 90% of the traffic). By optimizing the size of `AttestationData`, the aim is to reduce network load to improve node performance, and, most importantly, allow for greater throughput of other significant consensus data, such as Blobs. As a matter of fact, the current `Attestation` structure is not optimized for network transmission, leading to high bandwidth consumption. As a matter of fact, the application of Snappy block compression only reduces the size of an attestation by less than 10%. |
- may be a diagram with subnets subscribed with traffic a node experiences will provide a very nice context
There was a problem hiding this comment.
I do not actually have that for now, will work on it this week.
There was a problem hiding this comment.
ok let me know if you want to add that or you think this EIP is ready for draft?
g11tech
reviewed
Apr 3, 2024
g11tech
reviewed
Apr 3, 2024
Co-authored-by: g11tech <develop@g11tech.io>
Co-authored-by: Andrew B Coathup <28278242+abcoathup@users.noreply.github.com>
This was referenced Apr 16, 2024
13 tasks
SamWilsn
reviewed
Jun 11, 2024
| --- | ||
| eip: 7670 | ||
| title: Reduced Attestation Format | ||
| description: <Description is one full (short) sentence> |
There was a problem hiding this comment.
Suggested change
| description: <Description is one full (short) sentence> | |
| description: Introduces a shorter format for attestations transmitted on the gossip network. |
|
|
||
| ## Motivation | ||
|
|
||
| Attestations currently dominate the bandwidth usage of the Consensus Layer's gossip network (approx. 90% of the traffic). By optimizing the size of `AttestationData`, the aim is to reduce network load to improve node performance, and, most importantly, allow for greater throughput of other significant consensus data, such as Blobs. As a matter of fact, the current `Attestation` structure is not optimized for network transmission, leading to unnecessarily high bandwidth consumption. As a matter of fact, the application of Snappy block compression only reduces the size of an attestation by less than 10%. |
There was a problem hiding this comment.
Suggested change
| Attestations currently dominate the bandwidth usage of the Consensus Layer's gossip network (approx. 90% of the traffic). By optimizing the size of `AttestationData`, the aim is to reduce network load to improve node performance, and, most importantly, allow for greater throughput of other significant consensus data, such as Blobs. As a matter of fact, the current `Attestation` structure is not optimized for network transmission, leading to unnecessarily high bandwidth consumption. As a matter of fact, the application of Snappy block compression only reduces the size of an attestation by less than 10%. | |
| Attestations currently dominate the bandwidth usage of the Consensus Layer's gossip network (approx. 90% of the traffic). By optimizing the size of `AttestationData`, the aim is to reduce network load to improve node performance, and, most importantly, allow for greater throughput of other significant consensus data, such as Blobs. As a matter of fact, the current `Attestation` structure is not optimized for network transmission, leading to unnecessarily high bandwidth consumption. Furthermore, the application of Snappy block compression only reduces the size of an attestation by less than 10%. |
|
|
||
| ## Backwards Compatibility | ||
|
|
||
| Backward incompatible. |
There was a problem hiding this comment.
You should describe the backwards incompatibility. Like "clients using a pre-7670 network format will be unable to communicate with clients post-7670."
|
There has been no activity on this pull request for 2 weeks. It will be closed after 3 months of inactivity. If you would like to move this PR forward, please respond to any outstanding feedback or add a comment indicating that you have addressed all required feedback and are ready for a review. |
18 tasks
|
This pull request was closed due to inactivity. If you are still pursuing it, feel free to reopen it and respond to any feedback or request a review in a comment. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ATTENTION: ERC-RELATED PULL REQUESTS NOW OCCUR IN ETHEREUM/ERCS
--
When opening a pull request to submit a new EIP, please use the suggested template: https://github.com/ethereum/EIPs/blob/master/eip-template.md
We have a GitHub bot that automatically merges some PRs. It will merge yours immediately if certain criteria are met: