-
Notifications
You must be signed in to change notification settings - Fork 781
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
Decouple gossip #3950
Decouple gossip #3950
Conversation
}; | ||
crate::publish_pubsub_message(network_tx, PubsubMessage::BeaconBlock(block.clone()))?; | ||
|
||
/* TODO: publish all blob sidecars associated with this block */ |
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.
there's an open discussion whether to do blob publishing separately
ethereum/beacon-APIs#300
PR: ethereum/beacon-APIs#302
86e6906
to
55753f8
Compare
@pawanjay176 would it be helpful if we rebase this on the main blob branch and merge it? |
I think this will overlap with some of the caching stuff we are doing. But I can cherry pick the gossip validation changes in this PR and we can continue with the caching stuff in another PR. |
Relevant work extracted into #4092 |
Issue Addressed
N/A
Proposed Changes
Start decoupling gossip logic according to ethereum/consensus-specs#3244