ChainSafe / ChainSafe/lodestar
Use INITIAL_EPOCH in fork-choice filter_block_tree
Open
help wanted
prio-low
scope-ux
- Dominant language
- TypeScript
- Stars
- 1.4k
- Forks
- 483
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 156
Description
**Describe the bug**
Fixes a "UX" issue when syncing from weak subjectivity
- See issue https://github.com/ethereum/consensus-specs/issues/2566
and suggestion https://github.com/ethereum/consensus-specs/issues/2566#issuecomment-1165996834
Contributor guide
Research direction
Read the linked consensus-specs issue and suggestion first, then trace the filter_block_tree entry point to understand its epoch handling during weak-subjectivity sync. Done means filter_block_tree uses INITIAL_EPOCH as described and the related sync behavior is covered by the project's existing verification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- blockchain
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100