test: Add fuzz testing for contribution amounts and member counts

[cypriannwokolo2-creator]

Description

All contract functions must handle random/malformed inputs without panicking. Add fuzz testing for critical operations.

Requirements

• Add fuzz tests for contribution amounts (i128 range)
• Add fuzz tests for member counts (0..1000)
• Add fuzz tests for round numbers
• Ensure all fuzz tests return proper errors, never panic

Acceptance Criteria

• Fuzz tests run with random inputs
• No panics on any input
• All invalid inputs return proper errors
• Fuzz tests run in CI

Priority

Medium

[classicjoshua1-creator]

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

Hi Maintainer, I’ve looked through the issue and understand what needs to be done. I’d be glad to take it on and work toward a solid solution.

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

[abdulrcrtw]

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

Hello, I'd like to pick this issue up.

I'll add focused test coverage for this, following the existing test patterns already used in the repo.

Planned approach, based on the acceptance criteria:

• Fuzz tests run with random inputs
• No panics on any input
• All invalid inputs return proper errors
• Fuzz tests run in CI

I'd appreciate being assigned to this issue and look forward to contributing.

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

[nasirudeenbadirudeen87-cloud]

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

Maintainer, I’m happy to take this one. After reviewing the codebase, I’m comfortable with the approach and ready to get started. I’ll keep the scope focused, add solid test coverage, and ensure CI stays green. I’d be glad to open a draft early so we can confirm the direction together

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

[Ceepr1an]

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

I'd like to work on this issue

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

[dimin4241-svg]

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

I have practical experience writing Rust property and boundary tests for Soroban contracts. I reviewed the contribution and member-count paths and can add focused fuzz coverage that checks errors and overflow behavior without changing production semantics. I can complete this test work within 1–2 days of assignment. Please assign it to me.

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

[drips-wave]

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

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