lambdaclass / lambdaclass/lambda_ethereum_consensus
Make DB modules to use KvSchema
Open
Nobody has claimed this yet.
metrics
- Dominant language
- Elixir
- Stars
- 109
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
These modules can be modified to use the KvSchema module and unify how telemetry is collected + free methods.
- Blob DB
- Block DB
- Block states
- State DB
- Metadata
- Operations collector
- SubnetInfo
- Block by slot (now part of block db)
- Block status by root.
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 KvSchema module and each listed database module: Blob DB, Block DB, Block states, State DB, Metadata, Operations collector, SubnetInfo, Block by slot, and Block status by root. Compare their current telemetry collection and free methods, then verify that the modules use KvSchema consistently and expose unified behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- databases
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100