lambdaclass / lambdaclass/lambda_ethereum_consensus
Missing attestations and sync committee messages due to late subnet subscription
@rodrigo-o is already working on this.
Since Sep 19, 2024.
- Dominant language
- Elixir
- Stars
- 109
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
Previously part of #1279, I split the bug we were having from the leave and join that was made previously on duties calculations.
The bug is now this issue and it goes as follows:
Subscription to aggregation subnets happens just after attestation or sync committee broadcast, i.e. at the second third of a slot. There is also another place that could make produce this early and that's at the processing of a new block root. because of this, some sync committee messages and attestation were not part of aggregation, to solve this bug we need to subscribe as early as possible to the subnets that we need to be aware of.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.