[Contract] Treasury Allocation Percentages (Basis Points)

[gabito1451]

Independence Note: Execute solely using Rust native i128 logic matrices locally.

Context:
Guild treasuries often allocate funds to different sub-pools (e.g., 10% to community, 90% to development). Using basis points (BPS) is the standard for precision.

Objective:
Implement a utility to compute shares based on BPS.

Acceptance Criteria:

• Define 10000 as the maximum BPS (100%).
• Create a function calculate_share(total_amount, bps) -> i128.
• Ensure it uses checked multiplication to avoid overflows.
• Write unit tests for common values (e.g., 500 BPS = 5%, 1000 BPS = 10%).
• Ensure that for a total of 100 XLM, 10 BPS correctly results in 0.1 XLM represented in stroops.

Technical Pointers:

• BPS is preferred over percentages in finance to avoid rounding errors when dealing with small amounts.

[Emmanuelluxury]

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

I’m interested in working on this issue because it sits at the intersection of system reliability and developer experience—areas I care about deeply. Issues around package management, upgrades, and environment consistency can quietly slow teams down or introduce hard-to-debug problems. Fixing them not only improves stability but also makes the workflow smoother for everyone who depends on the tool.

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

[drips-wave]

Congratulations, @Emmanuelluxury! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on April 29, 2026.

🧑‍💻 @Emmanuelluxury: 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 @Emmanuelluxury as part of the Stellar Wave Program's 4th Wave 🥳

Moderator's reason: [Auto-assessed] The contributor has implemented the requested BPS utility with robust error handling and comprehensive unit tests that cover all acceptance criteria, including the specific Stellar stroop calculation. The code is well-documented and follows the technical requirements exactly.

😎 @Emmanuelluxury: You earned 200 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.