State Footprint & TTL Management (Persistent Storage)

[hman38705]

Descriptions:

🔒 Security & Maintenance

Issue #6:

Developer Goal: Manage the "Time to Live" (TTL) for market data to prevent data loss due to Soroban's state expiration.

Files to Modify:

• contracts/predict-iq/src/modules/markets.rs
• contracts/predict-iq/src/modules/bets.rs

Detailed Logic:

1. State Types: Distinguish between Instance (contract config/counters) and Persistent (large market data).
2. Bumping Strategy:
   • Every bet placed must call e.storage().persistent().bump_ttl(&DataKey::Market(id), LOW_THRESHOLD, HIGH_THRESHOLD).
   • LOW_THRESHOLD: ~1 day (ledger depth).
   • HIGH_THRESHOLD: ~30 days (ledger depth).
3. Archiving: Implement a prune_market(id) function that can only be called 30 days after a market is Resolved and all prizes are claimed.

Verification Checklist:

• Use soroban-cli to inspect the TTL of a market entry after multiple bets. Verify it stays above the minimum threshold.
• [ ] git checkout -b features/issue-1-advanced-payout-rewards
• Pr Request create your pr against develop branch[ ] git checkout -b features/issue-6-State Footprint & TTL Management (Persistent Storage)
• Pr Request create your pr against develop branch

---

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 200 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[Arome8240]

@Arome8240 has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Hello, I'm a smart contract and full stack developer, open for contributions. contributed to over 20 project on OnlyDust and Drips , with expertise in Solidity, Cairo, JavaScript, TypeScript, and RUST. I am passionate about building secure and scalable blockchain solutions, and I would love the opportunity to contribute my skills toward solving this issue

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

[Emmanuelluxury]

@Emmanuelluxury has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

I’d like to work on this issue because it sits at the intersection of system design, financial logic, and secure contract architecture — areas I actively specialize in and enjoy building within. The problem requires careful handling of state transitions, precision math, and security constraints, which makes it both technically meaningful and impactful to the overall reliability of the protocol.

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

[kelly-musk]

@kelly-musk has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

hey bro i would to work with you

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

[drips-wave]

Congratulations, @kelly-musk! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on February 26, 2026.

🧑‍💻 @kelly-musk: 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 issued 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 🌊

[Emmyt24]

@Emmyt24 has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

gm boss, i would love to work on this issue.

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

[drips-wave]

Congratulations, @Emmyt24! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on February 26, 2026.

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