Contributor Tiering & Metadata Badges

[Cedarich]

Description
Extend the contributor-registry to support on-chain "Badges" or tiers based on contribution history and reputation. Complexity: Medium (150 points) 🏅

Requirements and Context

• Background: Gamification and visual recognition increase contributor retention.
• Success Criteria (Done):
  • ContributorData includes a badges bitmask or vector.
  • award_badge(admin, contributor, badge_id) function.
  • Integration: Vault can check tiers to give multipliers in matching pools.

Suggested Execution

• Fork/Branch: feat/contributor-badges
• Implementation: Use simple integer IDs for badges to keep storage costs low.

Guidelines

• Complexity: Medium (150 points)

---

[CmxTop]

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

I'd like to work on extending the contributor-registry with badge/tier support including the award_badge() function and vault integration. I have experience with Rust and Soroban smart contracts.

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

[Chrisbankz0]

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

I would like to work on this issue because I have hands-on experience as a full-stack developer, having completed over 30 projects across multiple technologies including Python, JavaScript, and React. I’m confident in my ability to deliver efficient, high-quality solutions tailored to your needs.

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

[drips-wave]

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

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

[drips-wave]

This issue has been marked as completed by a Drips Wave moderator for @Chrisbankz0 as part of the Stellar Wave Program's 3rd Wave 🥳

Moderator's reason: [Auto-assessed] The contributor Chrisbankz0 addressed all requirements for Issue #427 in PR #436 of Pulsefy/Lumenpulse, including the badge bitmask, the award_badge function, and the vault-facing tier multiplier logic. The PR has been open for over 10 days without maintainer objections and includes a robust suite of unit tests.

😎 @Chrisbankz0: You earned 150 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

ℹ️ Note: This issue was marked complete via moderation. Points were issued even though the GitHub issue remains open.