NethermindEth / NethermindEth/Catalyst
Improve block verification thread
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 44
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
Start a block verification thread as soon as we become the Submitter. This is useful when the previous operator was ejected during the handover window, so we don’t need to wait for a new epoch to verify their blocks.
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 Submitter handover transition and the existing block verification thread. Reproduce or inspect the case where the previous operator is ejected during the handover window. Done means verification begins immediately upon becoming Submitter, without waiting for a new epoch.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- blockchain, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100