Optimized Data Layout for RefundHistory

[Cybermaxi7]

Theme: Part 7: Infrastructure & Scalability

• Context: Storing full refund history entries can be heavy.
• Acceptance Criteria:

[manueljnr1]

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

Hello, I’m a full stack developer with hands-on experience building with variety of tools including Nextjs, nodejs, nestjs, React, Typescript, python and more

I focus on writing clear, maintainable code and making sure features work as expected end to end, not just in isolation. I communicate progress regularly and keep things transparent as I work. I’m confident I can complete this task within an ETA of 4 HOURS

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

[drips-wave]

Congratulations, @manueljnr1! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on April 29, 2026.

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