Roadmap's "recurring MaintenancePool deposits" item remains unimplemented — deposit() is entirely manual despite the monthlyDeposit field implying an automatic cadence

[chonilius]

README.md's Roadmap lists: "Add a scheduled job for BountiesService.expireOverdue() (deadline sweeps) and recurring MaintenancePool deposits." The expireOverdue half is already tracked (see the existing dead-code/no-scheduled-job issues for it). The maintenance-pool half is not separately tracked: MaintenancePoolService.deposit() is exclusively triggered by a sponsor calling POST /maintenance-pools/:id/deposit — there is no @Cron-scheduled (or any other automated) recurring deposit mechanism anywhere in the codebase, despite MaintenancePool.monthlyDeposit and the entity's own doc comment ("Sponsors can deposit into it repeatedly (recurring funding...)") both implying an expected regular cadence. Today, if a sponsor forgets to manually re-deposit, nothing notices or prompts them — the "recurring" nature of a maintenance pool is purely a naming convention on the monthlyDeposit field, not an enforced or automated behavior.

[Syringe7]

I would love to work on this issue. please assign to me to work on it ASAP

[Chinonso-Peter]

@Chinonso-Peter has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Can i work on this issue

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

[tecmalik]

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

please sssign me to this issue i would love to woek on it

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

[damilare0813]

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

I'd be glad to handle this issue. I'll keep the implementation concise, maintainable, and well-documented

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

[Jerry-Tekh]

@Jerry-Tekh has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi repo maintainer , Please I am back again. i work on this repo and was merged correctly. please get me assigned to this issue . i will implement the correct fix and get it tested, thank you

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

[anuoluwaponiorimi]

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

Hii team, so good to have participated in this org in previous waves, If assigned to this, here's what I'll deliver: a working fix, tests covering the edge cases, and a clear PR description so review is fast on your end. I take contribution quality seriously — happy to point you to [Similar Past Work] as proof.

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

[drips-wave]

Congratulations, @anuoluwaponiorimi! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @anuoluwaponiorimi: 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 🌊