Repository navigation
Checkpoint keeper watch progress so a restart cannot resettle #380
Description
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.tsservices/keeper/src/dry-run.tsservices/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 Wavelabel on GitHub. That path defaults the issue to Trivial (100 points).
Activity
davidluxedesigns commentedon Sep 29, 2026
@davidluxedesigns has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @davidluxedesigns to this issue.
adeboladee commentedon Sep 29, 2026
@adeboladee has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @adeboladee to this issue.
Adeyemi-cmd commentedon Sep 29, 2026
@Adeyemi-cmd has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Adeyemi-cmd to this issue.
drips-wave commentedon Sep 29, 2026
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 🌊
Merge pull request #447 from adeboladee/feat/issue-380-keeper-watch-c…
grantfox-oss commentedon Oct 1, 2026
🎉 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.
feat(keeper): add round watch cursor checkpointing and restart resili…