lambdaclass / lambdaclass/lambda_ethereum_consensus
Store block headers and bodies separately in DB
Open
Nobody has claimed this yet.
needs elaboration
perf
- Dominant language
- Elixir
- Stars
- 109
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
Since some checks don't require the whole block, it might be useful to store both parts separately.
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 reviewing the existing block storage and the checks that do not require a whole block; the issue does not name specific files, tests, or entry points. The work is done when block headers and bodies are stored separately in the database and the relevant checks can use only the needed part.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100