Add a "Contract Storage Layout" reference for each contract

[Austinaminu2]

Summary

Developers building on top of StellarForge or auditing the contracts need to understand what data each contract stores and how it is keyed. There is no storage layout documentation.

Tasks

• Document all storage keys and their value types for each contract
• Add this to each contract's README under a ## Storage Layout section
• Note which keys are persistent vs temporary (Soroban storage types)

Labels: good first issue, documentation

[AbuJulaybeeb]

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

hi maintainer,
would like to take on this

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

[spiffamani]

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

Hey,

I'm a full-stack Software Engineer with 3 years of experience and a background in Blockchain development. I'm relatively new to open-source but I pick things up fast and I'm genuinely interested in this issue.
My main stack is React, TypeScript and Next.js on the frontend — I focus on clean component architecture, responsive design and performance. On the backend I work with Node.js, Java and Rust, handling everything from API design to database modeling.
A few things I've built:

https://www.zendvo.com/
https://cleanrest.vercel.app/

I'm comfortable jumping into an existing codebase, following conventions and shipping clean, maintainable code. My GitHub shows the kind of work I do better than I can describe it.
I'd love to take this on — thanks for considering me.

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

[nissinanlung]

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

I would love to work on this issue

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

[drips-wave]

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

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