lambdaclass / lambdaclass/lambda_ethereum_consensus
Process attestations from the aggregate_and_proof topic
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 109
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
Currently we're only processing attestations included in blocks. The call to ForkChoice.on_attestation from OperationsCollector is currently disabled, although that's probably a remanent from the time where ForkChoice performed a sync state transition. We should try re-adding it, and if it proves too much for the genserver we can try other strategies like batching/aggregating results and updating in a fixed frequency.
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.
Research direction
Start by tracing the aggregate_and_proof topic consumer and the OperationsCollector path, then inspect why the ForkChoice.on_attestation call is disabled. Re-enable the call experimentally and observe the ForkChoice genserver under attestation load; the work is done when attestations from that topic are processed reliably without overwhelming the genserver.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100