Lack of TTL protection for non-market governance records

[hman38705]

Description
While bump_market_ttl (Line 235) protects market data, other critical governance records like PendingUpgrade (Issue 32) and Guardian records might not have explicit TTL management called during their lifecycle. This puts long-running governance processes at risk of expiring and becoming unrecoverable during periods of inactivity.

Requirements and context

• Implement automated TTL bumping for all persistent governance data.
• Ensure critical protocol configuration never expires.

Suggested execution

• Fork the repo and create a branch: git checkout -b fix/issue-85-gov-ttl-management
• Audit all persistent storage usage.

Implementation changes

• Update governance.rs to include extend_ttl calls for all critical keys.

Test and commit

• Verify that a pending upgrade remains accessible even after 3 months of network inactivity.

Example commit message
fix: ensure consistent TTL management for all governance and protocol state

Guidelines

• Data durability.
• Timeframe: 24 hours.

[Bug-Hunter-X]

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

Hey Champ, Can i get on this and get it done?

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Bug-Hunter-X to this issue.

[onlydotsevn1]

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

I would like to work on this issue. My plan:

Audit all persistent storage keys in governance.rs and related modules to identify every record without explicit TTL management, including PendingUpgrade, Guardian, and any other critical protocol configuration
Add extend_ttl calls for all identified governance keys at the appropriate points in their lifecycle, such as on creation, update, and access
Align TTL bump values with the existing bump_market_ttl pattern for consistency across the protocol
Ensure critical records like PendingUpgrade remain accessible through extended periods of network inactivity

Tests will verify a pending upgrade remains accessible after simulated long inactivity, Guardian records do not expire during a governance process, TTL is correctly extended on each lifecycle event, and no governance state becomes unrecoverable.
Branch: fix/issue-85-gov-ttl-management
Commit: fix ensure consistent TTL management for all governance and protocol state
PR will include: Closes 188, ready within the 24 hour timeframe.
Please assign, happy to start immediately.
Thanks!

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

[fairbid01]

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

I would like to work on this issue. My plan:

Audit all governance-related storage keys to identify missing TTL protection
Add extend_ttl calls for critical records such as PendingUpgrade and Guardian data
Ensure consistent TTL management across the full governance lifecycle

Tests will confirm that governance records persist through long inactivity periods, remain accessible as expected, and no regressions occur in protocol state handling.

Branch: fix/issue-85-gov-ttl-management
Commit: fix ensure consistent TTL management for all governance and protocol state
PR will include: Closes issue #188, ready within the 24 hours.

Please assign, happy to start immediately.

Thanks!

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

[brite-side0]

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

Please i will love to work on this issue with you.
I’d like to implement consistent TTL management for all governance-related storage, ensuring critical records like PendingUpgrade and Guardian data never expire.
I will audit storage usage, add extend_ttl calls in governance.rs, and verify long-term data durability through testing.

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

[drips-wave]

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

🧑‍💻 @brite-side0: 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 @brite-side0 as part of the Stellar Wave Program's 3rd Wave 🥳

😎 @brite-side0: 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.