Property-based fuzz tests for all Stellar Soroban contracts

[truthixify]

Labels: Stellar Wave, stellar, test, drips, help-wanted
Tier: M (2–4 days)
Type: test

Context

Today every Stellar contract has unit tests, but no property-based / fuzz coverage. Stealth address payments are arithmetic-heavy and have many edge cases (empty payloads, oversized data, malformed addresses) — exactly the kind of thing where property tests pay off.

This issue adds a proptest-based test layer that lives alongside the existing unit tests.

Scope

Add proptest (or quickcheck if preferred — pick one and justify) as a dev-dependency in each of the four Stellar crates:

• stealth-announcer
• stealth-registry
• stealth-sender
• wraith-names

For each contract, write at least 5 properties that should always hold:

Examples

• announcer: For any (scheme_id, stealth_address, ephemeral_pub_key, metadata) where lengths are valid, announce() emits exactly one event with those fields verbatim.
• registry: register_keys then stealth_meta_address_of for the same (registrant, scheme_id) round-trips bit-for-bit.
• sender: batch_send of N transfers either fully succeeds (announcement count == N) or fully fails (announcement count == 0). Never partial.
• wraith-names: Any 3–32-char lowercase alphanumeric name registered, then resolve()'d, returns the exact meta-address passed in. Any name outside that grammar panics.

Coverage requirement

Run with proptest! cases ≥ 1024 by default; ≥ 16384 in CI nightly job. Report any flaky tests; we'd rather find non-determinism now than in production.

Acceptance criteria

• proptest dev-dependency added to all four Stellar crates.
• tests/properties.rs in each crate with at least 5 properties.
• CI nightly job that runs with the larger case count, alongside the existing test job.
• README section "Property tests" explaining how to add new ones.
• Any bugs surfaced by the new tests are filed as separate issues.

Resources

• proptest book: https://proptest-rs.github.io/proptest/
• Stellar soroban-sdk testutils: https://docs.rs/soroban-sdk/latest/soroban_sdk/testutils/

[bbkenny]

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

Hi! I'd love to write property-based fuzz tests for Wraith's Soroban contracts. I understand that stealth address payments are math-heavy and have many edge cases that standard unit tests might miss. I have experience writing proptest layers for other rust/soroban smart contracts. My approach will be to set up a comprehensive fuzz test layer covering overflow safety and invalid input rejections. Ready to write!

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

[Heazzy500]

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

Hi Maintainer, I’d like to work on this issue. I have experience handling similar tasks and can start immediately.

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

[Samaro1]

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

Gm gm boss, I would love to work on this issue. A satisfactory PR will be raised in 8 hours tops

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

[drips-wave]

Congratulations, @bbkenny! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

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