-
-
Notifications
You must be signed in to change notification settings - Fork 311
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
Always add gossip attestations to forkchoice #5259
Always add gossip attestations to forkchoice #5259
Conversation
Performance Report✔️ no performance regression detected Full benchmark results
|
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.
Are you sure this is required? What problem or correctness issue is it trying to fix?
@dapplion right now we only pass attestations to fork_choice if we have an aggregator on that subnet/slot, I don't see any requirements for that. I checked from the spec: also this was instructed from Cayman as I remember, could you double check @wemeetagain ? |
Right, if we have already done the work of verifying the attestation, might as well include it in the fork-choice |
🎉 This PR is included in v1.7.0 🎉 |
Motivation
Description
attnetsService.shouldProcess
should only decide if we add attestation to our pool to prepare for aggregator's duty later