lambdaclass / lambdaclass/lambda_ethereum_consensus
Pessimistic Sync
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 109
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
After the recent Holesky issue it was discussed that CL clients want to support the ability to disable optimistic sync altogether as a feature flag. I need to go through our current implementation of syncing because AFAIK it's just using Optimistic sync but this could become an umbrella issue to follow other related ones.
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 the current syncing implementation and identifying where optimistic sync is assumed. Review the Holesky-related context and existing related issues, then define the scope of the umbrella issue. Done means the required feature-flag behavior and follow-up work are clearly specified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100