Add contract fuzz testing

[big14way]

Set up fuzz testing for contract functions to find edge cases.

Acceptance Criteria:

• Configure cargo-fuzz or honggfuzz
• Add fuzz targets for create_group, contribute, distribute_payout
• Test with random inputs including boundary values
• Document found issues

Files: new directory contracts/sorosave/fuzz/

[jiarongmai]

I can implement this feature. I have experience with similar tasks and can deliver high-quality code. Ready to start immediately!

[TUPM96]

/attempt #36

Plan: add cargo-fuzz configuration under contracts/sorosave/fuzz, create fuzz targets for create_group, contribute, and distribute_payout, document how to run them and current findings, and validate the normal contract test suite still passes. Payout details can be provided privately if accepted.

[TUPM96]

/claim #36

PR opened: #152

Added cargo-fuzz configuration and fuzz targets for create_group, contribute, and distribute_payout, plus run documentation. Payout details can be provided privately on acceptance.

[Hobie1Kenobi]

Approach

I will set up cargo-fuzz in the contracts/sorosave/fuzz/ directory. Using the arbitrary crate, I'll define structured corpus generators for the required functions (create_group, contribute, distribute_payout) to ensure boundary values (e.g., max/u128, zero amounts, empty strings, overflow inputs) are efficiently targeted alongside random inputs. I will execute the fuzz targets for a baseline cycle to identify any panics, overflows, or logic edge cases, and log the results.

Deliverables

1. Fully configured cargo-fuzz environment in contracts/sorosave/fuzz/.
2. Fuzz targets for create_group, contribute, and distribute_payout with structured input generation.
3. Initial corpus and boundary-value test cases.
4. Documentation of any discovered edge cases/issues (or confirmation of stability).
5. Brief README.md explaining how to build and run the fuzz targets.

ETA

3 days

Payout Address

0x408f39B19266022FeC03076091e59D1f4f163658