NethermindEth / NethermindEth/Catalyst
AnchorOffset problem
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 44
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
We have MAX_ANCHOR_HEIGHT_OFFSET_REDUCTION_VALUE set to 10. We need to ensure that we can land our transaction within 10 slots. Possibly increase it after Taiko increases the maxAnchorOffset value
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 references to MAX_ANCHOR_HEIGHT_OFFSET_REDUCTION_VALUE and trace how it affects transaction landing. Compare the current value of 10 with Taiko's maxAnchorOffset behavior, then determine whether transactions reliably land within 10 slots. Done means the setting and its validation are aligned with the supported Taiko limit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- blockchain
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100