[Contracts] Extend storage TTL to prevent stream entries from being archived

[ogazboiz]

Join the discussion on Telegram

Why this matters

Soroban persistent storage entries are not permanent — every entry has a Time To Live (TTL) and is archived once it expires, after which reads fail until the entry is restored. The StreamContract writes every stream to persistent storage in save_stream (contracts/stream_contract/src/storage.rs) and the protocol config to instance storage, but nothing in the contract ever extends those TTLs. A long-running stream (e.g. a 1-year salary stream) can have its on-chain state archived out from under it, causing withdraw, cancel_stream, and view calls to fail even though the stream is logically still active. For a payment-streaming protocol where streams are explicitly designed to live a long time, this is a correctness/availability gap that must be addressed before mainnet.

Acceptance criteria

• Extend the persistent TTL of a stream entry whenever it is read or written (e.g. in save_stream / load_stream in contracts/stream_contract/src/storage.rs, or after each mutating op in lib.rs) using env.storage().persistent().extend_ttl(...).
• Extend the instance TTL covering ProtocolConfig and the stream counter on each mutating entry point.
• Define sensible threshold/extend-to constants (documented) rather than magic numbers.
• Add a unit test in contracts/stream_contract/src/test.rs that advances the ledger past a short TTL and asserts the stream is still readable after a mutating call bumped it.
• Document the TTL strategy in code comments.

Files to touch

• contracts/stream_contract/src/storage.rs
• contracts/stream_contract/src/lib.rs
• contracts/stream_contract/src/test.rs

Out of scope

• A separate keeper/cron service to bump TTLs off-chain (this issue is about in-contract bumping only).
• Storage archival restoration UX in the frontend.

[Timi16]

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

I would love to work on this

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

[drips-wave]

Congratulations, @Timi16! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

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

[drips-wave]

This issue has been completed by @Timi16 as part of the Stellar Wave Program's 5th Wave 🥳

😎 @Timi16: 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. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.