We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug
Due to the same reason to #4600, a lot of SyncCommittee were missed
because SyncCommittee messages are submitted right at 1/3 slot which is a very busy time of the node
Expected behavior
Based on the spec https://github.com/ethereum/consensus-specs/blob/dev/specs/altair/p2p-interface.md#sync_committee_subnet_id we could submit SyncCommitteeSignature early right after we see new head (unlike Attestation where we're worry if the attestation is too early, it may reach a node before block and the attestation is ignored)
The text was updated successfully, but these errors were encountered:
twoeths
Successfully merging a pull request may close this issue.
Describe the bug
Due to the same reason to #4600, a lot of SyncCommittee were missed
because SyncCommittee messages are submitted right at 1/3 slot which is a very busy time of the node
Expected behavior
Based on the spec https://github.com/ethereum/consensus-specs/blob/dev/specs/altair/p2p-interface.md#sync_committee_subnet_id we could submit SyncCommitteeSignature early right after we see new head (unlike Attestation where we're worry if the attestation is too early, it may reach a node before block and the attestation is ignored)
The text was updated successfully, but these errors were encountered: