Add TTL bump on resolution storage reads (buffer #19)

[greatest0fallt1me]

Description

This is a smart-contract issue for the GrantFox campaign. This is a smart-contract issue for the GrantFox FWC26 campaign. Bump storage TTL on hot read paths in resolution.

Requirements and Context

• Implement per the description
• Add focused tests
• Document any API/visible changes
• Adhere to repo's lint and code style
• Must be secure, tested, and documented
• Should be efficient and easy to review

Suggested Execution

1. Fork the repo and create a branch

   git checkout -b task/resolution-ttl

2. Implement changes
   • contracts/resolution/src/lib.rs
3. Test and commit
   • Run the repo's standard test suite and lint
   • Cover edge cases; include output in the PR

Example commit message

fix: TTL bump on resolution

Acceptance Criteria

• Implementation matches the description
• Tests added and passing
• Code review approved
• Docs updated

Guidelines

• Minimum 95% test coverage with cargo test
• require_auth on every state-changing entrypoint
• Overflow-safe math; no unwrap() in production paths
• Clear NatSpec-style /// rustdoc
• Timeframe: 96 hours

[legend-esc]

@legend-esc has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

’d like to work on this issue because it addresses an important area of the project and presents a great opportunity to make a meaningful contribution. I’m particularly interested in delivering a solution that is reliable, maintainable, and aligned with the project’s existing architecture and development standards.

I have experience working across software development, including backend and frontend development, APIs, databases, testing, DevOps, and blockchain-based applications. I’m comfortable understanding existing codebases, identifying the root cause of issues, implementing clean and scalable solutions, and writing thorough tests to prevent regressions.

My approach would be to first understand the existing implementation and project conventions, then develop the solution in a focused and incremental way. I’ll ensure the changes are well-tested, documented where necessary, and do not introduce unnecessary complexity or break existing functionality. I’m also committed to clear communication, responding to review feedback, and delivering a polished contribution that provides real value to the project.

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

[drips-wave]

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

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

[greatest0fallt1me]

Hey @legend-esc 👋 — you've been assigned to this issue based on your DripsWave application.

Quick reminders:

• Draft PR early and link it with Closes #<issue-number> so the DripsWave bot auto-closes.
• Please respect the 4 assignments per org cap (DripsWave auto-unassigns beyond that).
• Ping in Discord for questions or unblocks: https://discord.gg/WC53JxDqx

Looking forward to your PR — good luck! 🚀