No support for proposal categories or tags

[PrincessnJoy]

Description: All proposals are in a single flat list with no categorization. As the number of proposals grows, users cannot filter by topic (e.g., "Treasury", "Protocol Upgrade", "Community").

Acceptance Criteria:

• Add an optional category: Option<String> field to Proposal (max 32 chars, from a predefined list)
• Add category filter to the frontend proposal list
• Define the initial category list in the contract or as a governance parameter

Priority: Low
Estimated Effort: Medium
Dependencies: None
Labels: enhancement, feature, governance

---

[CNduka001]

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

I will help you manage the assignment of categories. Rough code irks me too
ETA 3 hrs
please assign

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

[joshyy564]

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

please assign

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

[drips-wave]

Congratulations, @joshyy564! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

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