No GitHub Issue templates

[chonilius]

There's no .github/ISSUE_TEMPLATE/ directory — issues on this repo are filed freeform. Given the issues are the bounty inventory for this platform (per README.md's own description of the product), structured issue templates (e.g. a "Bug report" form capturing repro steps/affected contract/severity, and a "Feature request" form) would make new issues more consistently bounty-ready — easier for a contributor to scope and estimate, and easier for a maintainer to price and label — than relying on every filer to freehand the level of detail this repo's existing issues clearly aim for.

[graceanya796-maker]

@graceanya796-maker has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hello
I would love to work on this issue please

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

[cristianooR7]

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

hello miantainer, i would like to work on this

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

[drips-wave]

Congratulations, @cristianooR7! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

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