NethermindEth / NethermindEth/Catalyst
Improve L2 head unexpected change
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 44
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
Track the safe and unsafe L2 heads. If the L2 head changes to safe, it means the driver has restarted, and we need to resubmit the same L2 blocks to unsafe head
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 locating the L2 head handling and the driver restart path; no files or tests are named in the issue. Trace how safe and unsafe heads are currently tracked, then verify that a change to a safe head causes the same L2 blocks to be resubmitted to the unsafe head.
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
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100