lambdaclass / lambdaclass/ethlambda
Pending blocks in DB are never pruned
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 82
- Forks
- 28
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 20
Description
We currently don't prune pending blocks. We should start doing that both from memory, and from our DB
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 how pending blocks are stored in memory and in the database. Determine the project's pruning conditions and apply them consistently to both locations; done means obsolete pending blocks are removed from memory and the DB without affecting valid blocks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- blockchain, databases, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100