lambdaclass / lambdaclass/lambda_ethereum_consensus
[Attestation refactor] Store only aggregation bits and signatures
Open
Nobody has claimed this yet.
good first issue
- Dominant language
- Elixir
- Stars
- 109
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
In SubnetInfo, we shouldn't store a list of entire Attestations since they all share the same AttestationData.
Originally posted by @Arkenan in https://github.com/lambdaclass/lambda_ethereum_consensus/pull/1136#discussion_r1634811128
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 locating the SubnetInfo definition and its use of Attestations, then trace how the shared AttestationData, aggregation bits, and signatures are read and updated. Compare the discussion in pull request #1136, and consider the work complete when SubnetInfo stores only the shared data plus the required bits and signatures without breaking its consumers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- blockchain
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100