Add fuzz testing for the API server's validation layer beyond `validation_fuzz_tests.rs`

[fejilaup-cloud]

Labels: testing, security
Priority: Medium
Estimated Time: 2 hours

Description:
api-server/src/validation_fuzz_tests.rs exists. Confirm it covers the request bodies for all endpoints that will be wired to real RPC calls (#36–#47), not just an initial subset.

Tasks:

• Extend fuzz targets to cover every public request schema in schemas.rs
• Run fuzzing in CI on a time-boxed schedule (e.g. nightly) rather than only locally
• Document any crashes/panics found and their fixes

[chukwunazannakenyi-netizen]

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

Hi maintainer I would like to work on this issue

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

[Deevhyne1023]

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

Hi, I've looked into this issue and I'm confident I have the relevant experience to implement a proper solution that meets the acceptance criteria. I'd welcome the chance to take this on and can begin promptly once assigned, thank you

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

[TheWeirdDee]

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

I’d like to work on #886, extending fuzz coverage across the API validation layer and ensuring it runs continuously in CI.

I’ll first audit api-server/src/validation_fuzz_tests.rs against every public request schema defined in schemas.rs, identifying any schemas used by the RPC-facing endpoints from #36–#47 that are currently missing coverage. I’ll then extend the existing fuzz targets using the repository’s established testing patterns rather than introducing unnecessary infrastructure.

The fuzzing coverage will exercise malformed, boundary, empty, oversized, and structurally unexpected inputs for every public request schema, with particular attention to validation paths that could panic or incorrectly accept unsafe data.

I’ll add a time-boxed CI fuzzing job, preferably on a nightly schedule, while keeping normal PR CI deterministic and appropriately scoped. Any discovered crashes or panics will be reproduced with focused regression tests and documented alongside their fixes.

Validation will include the complete existing test suite, the expanded fuzz targets, and the new scheduled CI configuration. I’ll verify that every public schema has an associated fuzz target and that the fuzz job has a clear runtime limit so it cannot run indefinitely.

The change will remain focused on validation security and fuzz coverage, with no unrelated API behavior or RPC implementation changes. The PR will reference Closes #886 and include the schemas audited, fuzz cases added, CI configuration, exact validation commands/results, and details of any crash findings or fixes.

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

[Yusufolosun]

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

Hi Maintainer, Good day
Please can you entrust the implementation of this issue to me. I am a Full Stack Developer and I can deliver maintainable solution that align with your codebase

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

[pleasureiliya69-ops]

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

I would like to work on this issue.

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

[Oluwasuyi-Oluwatimilehin-Daniel]

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

Hello @maintainer, I’d like to work on this issue. I have experience handling similar tasks and can start immediately. And I will deliver at the shortest possible time.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Oluwasuyi-Oluwatimilehin-Daniel to this issue.

[GauravKarakoti]

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

Allow me to work on this one

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

[DeFex-lab]

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

Hi Maintainer! I’m interested in contributing to this task and can work toward delivering a clean solution on time.

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

[OmniZlatoon]

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

Sir please assign me your issues. I am desperate to work but issues are scarce. my Eta is 5 hours max.

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

[ayandipe]

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

Hi maintainer,
Kindly assign issue to me. I offer prompt and precise resolution.
Regards

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

[Adotse10066]

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

I will love to work on this issue please. I deliver high impact solutions, ensuring seamless workflow and client satisfaction

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

[ToryMic]

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

Hey, I've checked your issue and I can work on it.

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