Create Property-Based Tests for Payout Logic

[Yunusabdul38]

Description

Utilize property-based testing (using crates like proptest) to verify that the payout and fee logic holds true for any valid combination of stakes and outcomes.

Tasks

• Define properties (e.g., "Total amount claimed + fees must equal total amount staked").
• Set up property-based test runners for the claim_winnings logic.
• Fix any discovered precision or arithmetic issues.

Dependencies

• Issue Implement Safe Math Wrapper for Proportion Calculations #304
• Issue Increase Unit Test Coverage for Edge Cases #327

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 200 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

[Iwueseiter]

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

Hello Maintainer,

My name is Iwueseiter, and I am a smart contract developer with solid experience in Rust. I have previously contributed to Stellar open-source projects and am familiar with the ecosystem and contribution standards.

I am confident in my ability to implement the task as specified, following best practices and project guidelines. I can deliver the solution within an estimated timeline of 2 days.
Thank you for your consideration.

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

[Amarjeet325]

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

Hi maintainers 👋
I’d like to work on this issue.
I’m a full-stack developer and have previously contributed to multiple open-source projects.

Could you please assign this issue to me?

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

[Fidelis900]

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

i would like to apply for this issue sir.

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

[Emmanuelluxury]

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

I’d like to work on this issue because it sits at the intersection of system design, financial logic, and secure contract architecture — areas I actively specialize in and enjoy building within. The problem requires careful handling of state transitions, precision math, and security constraints, which makes it both technically meaningful and impactful to the overall reliability of the protocol.

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

[drips-wave]

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

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