lambdaclass / lambdaclass/lambda_ethereum_consensus
Simplify/Unify current_slot calculation
Open
Nobody has claimed this yet.
P2
- Dominant language
- Elixir
- Stars
- 109
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
As discussed at #1316, there are multiple ways to calculate the current slot, we need to unify and simplify them to avoid confusion or unintended bugs using one or the other.
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
Review the discussion in issue #1316, then locate the multiple current_slot calculation paths in the repository. Compare their behavior and unify them into one calculation approach; done means the competing paths are simplified without changing the intended slot behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- distributed-systems
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100