CONTRACTS: Implement Token Burning Mechanism

[truthixify]

Description
Add functionality to burn (permanently destroy) tokens with proper authorization checks and event emission for tracking burned tokens.

Files to Modify

• contracts/manage_hub/src/membership_token.rs - Add burn functionality
• contracts/manage_hub/src/lib.rs - Add burn endpoint
• contracts/manage_hub/src/events.rs - Add burn event
• contracts/manage_hub/src/types.rs - Add burn authorization types

Key Changes Required

• Burn Function - Implement token burning with ownership verification
• Authorization - Add role-based permissions for burning tokens
• Event Emission - Emit events when tokens are burned
• Supply Tracking - Update total supply counters after burning
• Burn History - Maintain record of burned tokens
• Batch Burning - Support burning multiple tokens in one transaction

Acceptance Criteria

• Implement burn_token function with proper authorization
• Add BurnToken event with token ID and burner address
• Update total supply after burning
• Prevent burning of non-existent tokens
• Add batch_burn function for multiple tokens
• Include burn reason/metadata in events
• Add query function to retrieve burn history
• Implement burn restrictions based on token state

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 100 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[7maylord]

@7maylord has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Hi, can i work on this issue, i have soroban smart contract writing experience.

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

[Kanasjnr]

@Kanasjnr has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

This is straightforward contract-level logic and I can implement
I’m a blockchain engineer with hands in experience with rust

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

[drips-wave]

Congratulations, @Kanasjnr! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on February 26, 2026.

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