Add a protocol revenue split function distributing accumulated treasury fees to stakers across all keys

[Chucks1093]

Summary

Protocol fees accumulate in the treasury but are never redistributed on-chain. A distribute_protocol_revenue function that splits the treasury balance pro-rata across all stakers weighted by their staked key value would create a meaningful on-chain yield for long-term stakers.

Scope

• Add distribute_protocol_revenue(snapshot_id: u32) callable only by the protocol admin
• Require an existing holder snapshot identified by snapshot_id to determine staker weights
• Compute each staker's share as their staked_quantity * current_price / total_staked_value
• Transfer each staker's share from the treasury to their wallet
• Emit a protocol_revenue_distributed event with total_distributed, staker_count, and snapshot_id

Acceptance Criteria

• Each staker receives the correct pro-rata share of treasury balance
• Unknown snapshot_id panics with SnapshotNotFound
• Non-admin caller panics with Unauthorized
• Dust from floor division retained in treasury
• protocol_revenue_distributed event emitted with correct fields

ETA: 24 hours

---

Coordinate on Telegram

[Seunfunmi-319509]

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

kindly assign

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

[adelekevictor12]

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

Hello maintainer, i can fix this issue

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

[shinorh247]

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

Hi maintainer I would like to work on this issue

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

[muhsar27]

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

Kindly assign

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

[Gojv-byte]

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

hello maintainer please assign

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

[somotochukwu-dev]

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

Hi
Please assign this issue to me
Thanks

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

[chainsmt]

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

Hi, I'd like to work on this issue please.

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

[drips-wave]

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

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