Repository navigation
Add Event Processing Checkpoints #783
Description
Activity
@temisan0x has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
Good day team, please i’d like to take on this issue
ℹ️ Repo Maintainers: To accept this application, review their application or assign @temisan0x to this issue.
@Jessepriase has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
i would like to work on this issue
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Jessepriase to this issue.
@Irhocko has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
Hi Maintainer, i will like to work on this issue, please assign it to me.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Irhocko to this issue.
Congratulations, @Jessepriase! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on September 30, 2026.
🧑💻 @Jessepriase: 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 🌊
This issue has been marked as completed by a Drips Wave moderator for @Jessepriase as part of the Stellar Wave Program's 9th Wave 🥳
Moderator's reason: [Auto-assessed] The PR has an open status with no maintainer response across any of the four channels, and a thorough code contribution (PR #820) that implements checkpoint persistence, restoration, and comprehensive unit tests addressing all requirements of issue #783.
😎 @Jessepriase: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here.
🧑💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.
ℹ️ Note: This issue was marked complete via moderation. Points were issued even though the GitHub issue remains open.
- added a commit that references this issue
on Oct 5, 2026 🎉 This issue has been marked as completed on GrantFox!
@Jessepriase's PR #820 was approved and merged by @Abd-Standard.
🏆 @Jessepriase: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (809 total points). Track your full progress on GrantFox.
👏 Great work, @Jessepriase! Keep contributing to Core-Foundry.
Description:
Persist the latest successfully processed ledger position so the listener can resume from a known checkpoint after interruption.
Scope:
Store processing checkpoints.
Update checkpoints after successful processing.
Resume from the last valid checkpoint.
Acceptance Criteria:
Restarting the listener does not require processing the entire history.
Checkpoints are only advanced after successful processing.
Recovery behavior is covered by tests.