Add Storage Access Pattern Analyzer

[Timi16]

Description

Analyze storage access patterns during execution and report which keys are read most frequently, which are write-heavy, which are read but never written, and suggest caching opportunities.

Requirements

• Track every storage read and write with counts
• Identify hot keys (read more than 5 times)
• Flag keys read repeatedly with no writes (caching opportunity)
• Display as a sorted frequency table after execution
• Include in JSON output

Suggested Execution

1. Branch: git checkout -b feature/storage-pattern-analyzer
2. Update src/inspector/storage.rs to track per-key access counts
3. Build access pattern report from collected data
4. Identify and label caching opportunities
5. Display sorted by frequency
6. Commit: feat: add storage access pattern analyzer

Acceptance Criteria

• All reads and writes tracked per key
• Hot keys (5+ reads) identified and labeled
• Caching suggestions shown for repeated reads
• Results sorted by frequency
• Tests with access-heavy test contracts

[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

[nonso7]

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

Can I work on this issue. I will deliver in 24 hour

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

[drips-wave]

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

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