lambdaclass / lambdaclass/lambda_ethereum_consensus
Address pre-finalized-checkpoint attestations
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 109
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
Currently, we're just ignoring attestations for unknown blocks. I guess we should check that the block exists, but discard the LMD/Casper votes? (since we would need past states to actually compute them). However, we should compare against other implementations.
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 handling of attestations for unknown blocks and compare that behavior with other implementations, as requested in the issue. Determine whether the block should be validated and whether LMD/Casper votes should be discarded when past states are unavailable; the issue provides no named files or tests for verification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100