TTL expiration behavior is only simulated in tests and not reflected by contract storage assertions

[grantfox-oss]

Description: storage_test.rs claims TTL should expire inactive records but the Soroban test environment does not validate it. Implement deterministic expiry utilities or update docs to avoid false confidence.

• Impacted files: app/contract/contracts/Folder/src/storage.rs, app/contract/contracts/Folder/src/storage_test.rs, app/contract/contracts/Folder/src/test.rs, app/contract/contracts/Folder/src/types.rs, app/contract/docs/UPGRADE_SAFETY_GATE_TEST_GUIDE.md, app/contract/README.md

[egwujiohaifesinachiperpetual-max]

Hello boss, Please assign this issue to me. i checked it out and im confident i will solve it
my eta is 4 hours

[Alanwiz00]

I'd like to work on this.

I reviewed the current TTL tests, and I think the issue is exactly as described: they're conflating contract-level expiry with Soroban storage TTL.

EscrowEntry.expires_at is business logic driven by env.ledger().set_timestamp(), and that's already covered elsewhere. Storage TTL, however, is based on ledger sequence numbers and the rent model. Advancing the timestamp doesn't exercise get_ttl_policy() or set_or_extend_ttl(), so tests like test_ttl_expiry_of_inactive_record can pass regardless of whether the TTL logic is working.

My plan is to:

• Add deterministic helpers for asserting storage TTL using env.storage().persistent().get_ttl(...).
• Drive TTL progression with ledger sequence numbers rather than timestamps.
• Add real before/after assertions for TTL extension on activity and expiry behaviour, documenting any limitations of the Soroban test environment where eviction isn't automatic.
• Rename or clarify the existing tests where necessary so they don't imply TTL eviction is being verified when it isn't.
• Update the accompanying documentation to explain the distinction between business expiry and storage TTL.

One small thing I noticed while reviewing: the issue references app/contract/docs/UPGRADE_SAFETY_GATE_TEST_GUIDE.md, but the file appears to live at app/contract/UPGRADE_SAFETY_GATE_TEST_GUIDE.md.

[grantfox-oss]

🦊 GrantFox — @Alanwiz00 has been assigned to this issue as part of the Official Campaign | FWC26 campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #330)
2. Your PR will be reviewed by the BlockDash-Studios maintainers

Good luck! Track your progress on GrantFox.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign | FWC26 campaign!

@Alanwiz00's PR #346 was approved and merged by @MaryammAli.

🏆 @Alanwiz00: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (191 total points). Track your full progress on GrantFox.

👏 Great work, @Alanwiz00! Keep contributing to BlockDash-Studios.