-
Notifications
You must be signed in to change notification settings - Fork 283
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
Fix sync committee when syncing #8192
Fix sync committee when syncing #8192
Conversation
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.
LGTM
@rolfyone I'm not a fan of the solution for the sync committee. The aggregate is fine. dumping some messages wrote in chat:
|
...reum/spec/src/main/java/tech/pegasys/teku/spec/executionlayer/ExecutionLayerChannelStub.java
Outdated
Show resolved
Hide resolved
ultimately its 1 persistent duty for sync committees which is different to other dutes.. that's why the VC is doing more... I think it's practical overall, but it's definitely different to all the others... |
I think It is fine yes. We could be wrong only if the chain is not producing blocks for an entire epoch. In that case i don't think there would be enough block space to include them all. |
fixes #8005
The aggregation fix is non-controversial while the sync message is not that clean, but it is the easiest implementation I came up with so far.
Essentially we will stop producing sync committee message if the head we have is older than 32 slot, which means:
1- we are connected to a BN which is falling out of sync.
2- the chain is not production a block for more than entire epoch, we have bigger problems.
Documentation
doc-change-required
label to this PR if updates are required.Changelog