Storage Footprint Optimization: TTL & Archiving

[Cedarich]

Status: Open (Wave 3 – ops)
Labels: Contract, Performance
Complexity: Medium (150 points)

Summary
Implement Soroban storage best practices regarding Time-To-Live (TTL) and data archiving to keep costs low.
Tasks

• Set appropriate TTL for escrow records (e.g., 6 months).
• Add an "extend" function for long-running escrows.
• Implement a cleanup function for expired/refunded data to reclaim storage deposits.
  Acceptance Criteria
• Contract storage remains lean and minimizes user fees.

---

[Agbeleshe]

@Agbeleshe has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

Hey can I solve this? I'll implement comprehensive storage optimization for the Soroban contract by adding TTL management, extension functionality, and cleanup mechanisms to minimize storage costs and reclaim deposits from expired data. With 5 years of experience in smart contract optimization, Soroban storage patterns, and gas-efficient Solidity/Rust development, I'll create a production-ready storage management system that balances data persistence with cost efficiency.

I'll implement TTL configuration by setting appropriate expiration thresholds (e.g., 6 months = 15768000 ledger entries) for escrow records during creation using env.storage().set_ttl() or instance/ledger TTL methods, ensuring records automatically expire if not extended. For long-running escrows, I'll add an extend_escrow(escrow_id, additional_ledgers) function that requires authorization from either party and updates the TTL using extend_ttl(), with validation to prevent indefinite extensions. The cleanup function will iterate through expired escrow records (checking current ledger against stored expiration), verify they're in terminal states (completed, refunded, or expired), and use storage().remove() to delete entries, refunding the storage deposit to the contract or designated address. I'll include helper functions to query storage size and estimate costs, comprehensive tests for TTL enforcement, extension authorization, and cleanup logic with edge cases for concurrent operations, and emit events for all storage modifications to enable off-chain monitoring of storage health.

Important clarification needed: The issue mentions "user-initiated cancellations" in the description, but your implementation currently restricts this to admin-only via env::caller() == admin. This creates a disconnect between the stated user need and the implemented access control

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

[drips-wave]

Congratulations, @Agbeleshe! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on March 30, 2026.

🧑‍💻 @Agbeleshe: 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 marked as completed by a Drips Wave moderator for @Agbeleshe as part of the Stellar Wave Program's 3rd Wave 🥳

Moderator's reason: [Auto-assessed] The contributor implemented the requested TTL management and storage optimization features, including functions to extend escrow TTL and cleanup terminal escrow records. The PR has been merged and the issue is closed, indicating successful completion of the tasks.

😎 @Agbeleshe: You earned 150 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.

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

ℹ️ Note: This issue was marked complete via moderation. Points were issued even though the GitHub issue remains open.