Add a RECUR_NEXT id counter with read_next_recurring_id/write_next_recurring_id helpers, independent of the proposal id sequence

[thegreatfeez]

Smart Contract — New Feature

Summary

Recurring schedules need their own independent id sequence. This adds a RECUR_NEXT counter with helpers to read and advance it, kept separate from the proposal id counter.

Background

The contract already maintains a next_id counter for proposals, stored under an instance key and read/written through read_next_id/write_next_id in contracts/accord/src/lib.rs. Recurring schedules must have their own id sequence so the two types do not collide.

What Needs to Be Done

1. Add an instance storage key for the next recurring schedule id (for example RECUR_NEXT), independent of the proposal id counter.
2. Add read_next_recurring_id and write_next_recurring_id helpers mirroring the proposal id helpers.
3. Keep the recurring id counter's initialization and progression separate from the existing proposal sequence.

Acceptance Criteria

• The recurring id counter is stored independently of the proposal id counter.
• The helpers read and write the counter correctly.
• The existing proposal id counter is unchanged.

Files to Look At

• contracts/accord/src/lib.rs — add the helpers near the existing read_next_id/write_next_id

Difficulty: Medium

[olacodes-01]

@olacodes-01 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 because I understand the problem and have a clear approach to solving it. I look forward to implementing the solution and submitting a clean PR.

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

[mosharraftimes2018-dev]

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

I would like to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @mosharraftimes2018-dev 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 🌊