Add an ACTIVE_RECUR instance counter bounded by a new MAX_ACTIVE_RECURRING constant to cap storage cost

[thegreatfeez]

Smart Contract — New Feature

Summary

The number of active recurring schedules must be capped to control storage costs. This adds an ACTIVE_RECUR instance counter and a MAX_ACTIVE_RECURRING constant, mirroring the existing active-proposal cap.

Background

The contract caps active proposals at MAX_ACTIVE_PROPOSALS via a persisted ACTCNT counter, checked at creation and execute time in contracts/accord/src/lib.rs. Recurring schedules need the same guard: an active-schedule counter and a maximum constant, bounded to prevent unbounded storage growth.

What Needs to Be Done

1. Define a MAX_ACTIVE_RECURRING constant beside the existing MAX_ACTIVE_PROPOSALS.
2. Add an ACTIVE_RECUR instance storage key and read_active_recurring_count/write_active_recurring_count helpers mirroring the active-proposal helpers.
3. The counter should count both Active and Paused schedules.

Acceptance Criteria

• The contract defines a MAX_ACTIVE_RECURRING constant.
• The active-recurring counter is persisted in instance storage.
• The helpers read and write the counter correctly.

Files to Look At

• contracts/accord/src/lib.rs — add the constant and helpers near the active-proposal equivalents

Difficulty: Medium

[Olayinka93]

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

Hello, this issue aligns well with my skills and experience. I’m confident I can resolve it effectively and deliver a proper solution. Kindly consider assigning it to me.

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

[nasirudeenbadirudeen87-cloud]

@nasirudeenbadirudeen87-cloud 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 @nasirudeenbadirudeen87-cloud to this issue.

[Halima-1]

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

Hi maintainer… I would like to work on this issue , kindly assign it to me

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

[drips-wave]

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

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