lambdaclass / lambdaclass/lambda_ethereum_consensus
Speed up state pruning by adding db tables
Open
Nobody has claimed this yet.
perf
- Dominant language
- Elixir
- Stars
- 109
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
Instead of decoding each state to get the key_state.
Only if state pruning takes more than an epoch on mainnet.
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
The issue names no files, tests, or entry points. Start by measuring whether state pruning takes more than an epoch on mainnet, then trace the pruning path that decodes each state to obtain key_state. Done means adding suitable database tables so pruning can avoid that decoding when the threshold is exceeded.
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