ethereum-optimism / ethereum-optimism/optimism
kona-sp1-proposer: resolve foreign ancestors blocking refund claims
- Dominant language
- Go
- Stars
- 6.5k
- Forks
- 4k
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 145
Description
## Summary
Follow up to #22835. A proposer-created game can be blacklisted or retired and therefore eligible to recover its creation bond through refund mode, but resolving that game may still be blocked by an unresolved foreign ancestor.
PR #22835 intentionally does not add permissionless foreign-game resolution. It keeps refund recovery narrow: the proposer resolves and claims only its own disallowed games, and waits when an ancestor has not reached a resolvable state.
## Desired behavior
When an owned disallowed game is blocked by foreign ancestors, identify the minimal unresolved ancestor chain and permissionlessly resolve only ancestors whose on-chain clocks/status make resolution valid. Once the dependency is resolved, continue resolving the owned game and claim its refund-mode credit.
## Constraints
- Do not resolve active or otherwise unready foreign games.
- Preserve parent-before-child transaction ordering across cycles.
- Do not retain foreign games for bond claims or treat them as proposer-owned.
- Keep failures isolated so one foreign dependency does not block unrelated refund claims.
- Avoid a full-history startup scan.
## Acceptance criteria
- A scenario test covers an owned blacklisted/retired game blocked by a resolvable foreign ancestor.
- The foreign ancestor resolves before the owned game.
- The owned game's creation bond is subsequently unlocked and paid through refund mode.
- Unready foreign ancestors produce no resolution transaction.
Filed by an AI coding assistant at the user's request.
Contributor guide
Research direction
Start by tracing the refund-mode resolution flow and the existing scenario tests for proposer-owned disallowed games. Add coverage for a resolvable foreign ancestor and an unready ancestor, then verify parent-before-child ordering, refund-mode bond payment, and that unrelated claims remain unaffected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100