NethermindEth / NethermindEth/Catalyst
Improve re-anchoring
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 44
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
Store unsafe L2 blocks in memory to reduce the time needed to fetch them during re-anchoring
DEBUG taiko_preconf_avs_node::taiko: Fetched L2 blocks from 401 to 718 in 6393 ms
DEBUG taiko_preconf_avs_node::taiko: Fetched L2 blocks from 172 to 560 in 4027 ms
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 re-anchoring flow and the path that fetches L2 blocks, using the debug messages to understand where the repeated fetches occur. Determine how unsafe L2 blocks can be retained in memory during re-anchoring, and verify that repeated operations reduce the time spent fetching blocks without changing the re-anchoring result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, blockchain
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100