Skip to content

Checkpoint keeper watch progress so a restart cannot resettle #380

Closed
#447
Closed
Checkpoint keeper watch progress so a restart cannot resettle#380
#447
Assignees
adeboladee
Labels
Stellar WaveIssue proposed for the Drips Stellar Wave programarea: keeperPermissionless keeper servicecomplexity: highExpected high implementation complexitydrips-candidateCandidate for a Drips Stellar Wave

Description

@karagozemin
karagozemin
opened on Sep 29, 2026

Goal

Persist the keeper's per-round watch cursor so a crash after a successful reveal or settle does not broadcast that step again.

Why this is High

Watch mode, the dry-run planner, and the live submit path do not share a durable cursor. Restart behavior is an integration across those three, plus the on-disk format has to be safe to resume.

Requirements

  • Store round id, last completed step, transaction hash, and network in a local checkpoint.
  • On startup, skip steps the checkpoint marks complete after confirming the hash status.
  • Refuse to start if the checkpoint network or contract id does not match the process config.
  • Make the dry-run command print the checkpoint it would write without submitting.

Acceptance criteria

  • Restart after a confirmed settle does not submit settle again.
  • A checkpoint for a different contract id refuses to start.
  • Dry-run writes nothing and submits nothing.
  • Tests cover crash-before-checkpoint and crash-after-checkpoint with a fake clock.

Pointers

  • services/keeper/src/keeper.ts
  • services/keeper/src/dry-run.ts
  • services/keeper/scripts/lifecycle-e2e.ts

Validation

  • Keeper unit tests for both crash points

Drips

  • Drips Complexity: High
  • Expected Drips Points: 200
  • Add this issue from the Drips maintainer dashboard and set complexity to High.
  • Do not apply the Stellar Wave label on GitHub. That path defaults the issue to Trivial (100 points).

Activity

  1. karagozemin
    added
    drips-candidateCandidate for a Drips Stellar Wave
    complexity: highExpected high implementation complexity
    area: keeperPermissionless keeper service
    on Sep 29, 2026
  2. drips-wave
    added
    Stellar WaveIssue proposed for the Drips Stellar Wave program
    on Sep 29, 2026

  3. davidluxedesigns commented on Sep 29, 2026

    @davidluxedesigns
    davidluxedesigns
    on Sep 29, 2026 – with Drips Wave

    @davidluxedesigns has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

    Hello Maintainer, I’ve carefully reviewed the issue and understand the requirements. I’m confident I can resolve it effectively and meet the expected criteria.

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @davidluxedesigns to this issue.

  4. adeboladee commented on Sep 29, 2026

    @adeboladee
    adeboladee
    on Sep 29, 2026 – with Drips Wave
    Contributor

    @adeboladee has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

    Kindly assign this task to me maintainer,i would fix this bug and conflict free

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @adeboladee to this issue.

  5. Adeyemi-cmd commented on Sep 29, 2026

    @Adeyemi-cmd
    Adeyemi-cmd
    on Sep 29, 2026 – with Drips Wave
    Contributor

    @Adeyemi-cmd has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

    can i please work on this

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @Adeyemi-cmd to this issue.

  6. karagozemin
    assigned
    adeboladee
    on Sep 29, 2026

  7. drips-wave commented on Sep 29, 2026

    @drips-wave
    drips-wavebot
    on Sep 29, 2026 – with Drips Wave

    Congratulations, @adeboladee! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on September 30, 2026.

    🧑‍💻 @adeboladee: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

    Warning

    When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

    🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

    🌊 Happy Wave 🌊

  8. karagozemin
    closed this as completedin #447on Oct 1, 2026
  9. karagozemin
    added a commit that references this issue on Oct 1, 2026

    Merge pull request #447 from adeboladee/feat/issue-380-keeper-watch-c…

    8de1d66

  10. grantfox-oss commented on Oct 1, 2026

    @grantfox-oss
    grantfox-ossbot
    on Oct 1, 2026 – with GrantFox OSS

    🎉 This issue has been marked as completed on GrantFox!

    @adeboladee's PR #447 was approved and merged by @karagozemin.

    🏆 @adeboladee: You earned 40 FoxPoints for this contribution! Your current tier: Builder (1,246 total points). Track your full progress on GrantFox.

    👏 Great work, @adeboladee! Keep contributing to Sub-Rosa-Issue.

  11. karagozemin
    added a commit that references this issue on Oct 1, 2026

    feat(keeper): add round watch cursor checkpointing and restart resili…

    e89639c
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Stellar WaveIssue proposed for the Drips Stellar Wave programarea: keeperPermissionless keeper servicecomplexity: highExpected high implementation complexitydrips-candidateCandidate for a Drips Stellar Wave

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions