lambdaclass / lambdaclass/lambda_ethereum_consensus
BlocksDB: support multiple blocks per slot
Open
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 109
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
Currently, in BlocksDB there is a block root by slot index that only supports one block for any given slot. We should fix that.
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 BlocksDB implementation and the block-root lookup keyed by slot index. Trace how blocks are stored and retrieved, then update the relevant coverage so multiple blocks can coexist for one slot and verify that each remains accessible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- database
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100