lambdaclass / lambdaclass/lambda_ethereum_consensus
Re-enable attestations processing coming from gossip
Open
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 109
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
We need to re-enable these at least outside of mainnet. This task should include some performance analysis to see how can we do so that this doesn't become a bottleneck.
Some related readings / PRs:
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 at lib/lambda_ethereum_consensus/p2p/gossip/handler.ex lines 33-34 and review issue #752 plus the linked EIP and performance discussion. Determine how attestations can be re-enabled outside mainnet, measure whether processing creates a bottleneck, and document results showing the intended behavior and acceptable performance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- backend, distributed-systems, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100