Cache common derived state (program balance, fee config) across query_* function chains

[Jagadeeshftw]

Description

Read-only query functions in contracts/view-facade/src/lib.rs and contracts/escrow-view-facade/src/lib.rs call into contracts/program-escrow/src/lib.rs multiple times per transaction to fetch ProgramData and FeeConfig, each incurring a separate storage read cost. Introducing a per-invocation cache (using a RefCell<HashMap<u64, ProgramData>> or Soroban's temporary storage) to memoize reads within a single call chain would reduce redundant ledger I/O.

Requirements and context

• Add a QueryCache struct using Soroban temporary storage in contracts/view-facade/src/lib.rs
• Wrap all ProgramData and FeeConfig reads through QueryCache::get_or_load
• Benchmark before/after instruction counts in docs/query-cache-benchmark.md
• Must be secure, tested, and documented
• Should be efficient and easy to review

Suggested execution

Fork the repo and create a branch

git checkout -b feature/query-cache-program-balance-fee-config

Implement changes

• Update/Write contract: contracts/view-facade/src/lib.rs
• Write comprehensive tests: contracts/view-facade/src/tests/query_cache_tests.rs
• Add documentation: docs/query-cache-benchmark.md
• Include NatSpec-style doc comments
• Validate security assumptions

Test and commit

• Run tests: cargo test -p view-facade
• Cover edge cases
• Include test output and security notes

Example commit message

perf: add per-invocation query cache for ProgramData and FeeConfig reads

Guidelines

• Minimum 95 percent test coverage
• Clear documentation
• Timeframe: 96 hours

[aigbagbobila]

@aigbagbobila has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi Maintainer can I resolve this. Kindly assign

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

[drips-wave]

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

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