chore: add an issue template for Stellar Wave bounty issues matching the established format

[misrasamuelisiguzor-oss]

Description

Every Stellar Wave issue in this repo (247 of the last 249) follows the same Description / Requirements and context / Suggested execution / Example commit message / Guidelines structure, but .github/ has no ISSUE_TEMPLATE directory, meaning the format is maintained purely by convention/copy-paste rather than being codified.

This is repository-level tooling, configuration, or process rather than application code, but that doesn't make it lower stakes: onboarding friction, unclear ownership, and process gaps are consistently what determines whether a project with this much surface area (two contract trees, two backend trees, two frontend apps, a static dashboard, and an active external contributor program) stays maintainable as it grows or slowly accumulates inconsistency that nobody has the full context to untangle.

Given that this repository is actively recruiting outside contributors through the Stellar Wave bounty program (this issue included), the quality of its repository-level scaffolding, from CONTRIBUTING.md to CODEOWNERS to its issue and PR templates, has a direct and measurable effect on how many contributors are able to land a change successfully on their first attempt versus giving up in the setup phase.

Requirements and context

• Add .github/ISSUE_TEMPLATE/stellar-wave-bounty.md codifying the exact structure used across existing issues

Suggested execution

1. Fork the repo and create a branch

   git checkout -b chore/issue-template-stellar-wave
   

2. Implement changes

• Add the issue template file with the Stellar Wave label pre-applied

3. Test and commit

• Open the 'New issue' page in the GitHub UI and confirm the template appears

Example commit message

chore: add issue template for Stellar Wave bounty format

Guidelines

• Assignment required before starting
• PR description must include: Closes #[issue_id]
• Keep PR description professional and detailed

[Awwal-dev34]

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

Hello, I’d like to contribute to this issue and would appreciate the opportunity to work on it. Thank you.

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

[divysam]

@divysam 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 @divysam to this issue.

[precious1joe]

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

i would like to work on this issue kindly assign me

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

[AnibeAchema]

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

I’d like to work on this issue because it is a practical improvement that can make the repository easier to contribute to and help maintain consistency as the project grows. Codifying the existing Stellar Wave issue format into a reusable GitHub issue template would reduce repetitive manual work and make it easier for new contributors to understand the expected structure.

I have experience working with GitHub repositories, development workflows, documentation, and project structure. I’m comfortable working with Markdown and repository configuration files, and I can verify the template through the GitHub issue creation flow to ensure it works as expected. I’d be happy to contribute this improvement while keeping the implementation aligned with the repository’s existing conventions.

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

[kwest0002-lab]

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

please i will love to work on this

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

[drips-wave]

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

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