Add a RECUR persistent storage key and read_recurring_payment/write_recurring_payment helpers with TTL bumping

[thegreatfeez]

Smart Contract — New Feature

Summary

A recurring schedule must be persisted and kept alive in storage. This adds a persistent storage key and read/write helpers for schedules, mirroring how proposals are stored.

Background

Proposals are persisted through read_proposal and write_proposal in contracts/accord/src/lib.rs, stored under a persistent key by id and kept alive with a TTL bump via the existing bump_persistent helper. Recurring schedules need the same treatment under their own key.

What Needs to Be Done

1. Add a persistent storage key for recurring schedules (for example a RECUR key), keyed by schedule id.
2. Add read_recurring_payment and write_recurring_payment helpers mirroring read_proposal and write_proposal.
3. Bump the persistent entry's TTL on write using the existing bump helper, matching the proposal pattern.

Acceptance Criteria

• A schedule can be written to and read back from persistent storage by its id.
• Writing a schedule bumps its persistent TTL the way proposals do.
• Reading a missing schedule returns a not-found error consistent with the proposal path.

Files to Look At

• contracts/accord/src/lib.rs — add helpers near read_proposal/write_proposal and the storage key definitions

Difficulty: Medium

[OgbuKingsley166]

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

I’ve resolved similar problems in the past and am confident I can implement a clean, efficient fix quickly,if am given the opportunity.

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

[Marvy54]

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

Hello maintainer, I would like to work on and fix this issue. Kindly assign it to me

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