Add fuzz tests for `appeal_default`

[Levi-Ojukwu]

Description:

Acceptance Criteria:

• Property test that appeal flow never panics
• Test with random evidence hashes

Relevant Files: contracts/fuzz/src/lib.rs

---

[spiffamani]

I'm a full-stack Software Engineer
I'd love to take this on — thanks for considering me

[MoscowDev]

I'd be happy to take this issue on. I have experience building production-ready applications and collaborating effectively through GitHub workflows, including implementing features, resolving bugs, and submitting well-documented pull requests.

I'll carefully review the existing implementation, identify the root cause, and deliver a robust, maintainable solution that aligns with the project's architecture and coding standards. Before submitting my PR, I'll thoroughly test the changes to ensure reliability and avoid regressions.

My goal is to contribute high-quality, clean, and maintainable code while communicating clearly throughout the process and delivering a dependable solution in a timely manner.

[MoscowDev]

I'd be happy to take this issue on. I have experience building production-ready applications and collaborating effectively through GitHub workflows, including implementing features, resolving bugs, and submitting well-documented pull requests.

I'll carefully review the existing implementation, identify the root cause, and deliver a robust, maintainable solution that aligns with the project's architecture and coding standards. Before submitting my PR, I'll thoroughly test the changes to ensure reliability and avoid regressions.

My goal is to contribute high-quality, clean, and maintainable code while communicating clearly throughout the process and delivering a dependable solution in a timely manner.

[Theophilus131]

I'd like to work on this issue. I understand the goal is to strengthen the appeal flow by adding property-based tests to ensure it never panics and by testing with randomized evidence hashes. I'll implement the required tests to improve the contract's reliability and catch edge cases

[TheShnider]

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

Hi. I have reviewed this issue and would like to work on it.

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

[stephanieoghenemega-eng]

@stephanieoghenemega-eng has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

hello maintainer, kindly assign these issues to me. Thank you

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

[drips-wave]

Congratulations, @stephanieoghenemega-eng! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

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

😎 @stephanieoghenemega-eng: 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. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.