[Backend] createStream returns 500 instead of 400 for non-numeric/missing ratePerSecond, depositedAmount or startTime

[grantfox-oss]

Telegram (ask questions / claim the issue here first): https://t.me/+DOylgFv1jyJlNzM0

Why this matters

stream.controller.ts:73-74 calls BigInt(ratePerSecond) and BigInt(depositedAmount) BEFORE any validation guard. BigInt('abc') throws SyntaxError and BigInt(undefined) throws TypeError, but the catch only maps RangeError to 400 - every other throw falls through to the generic 500. So a malformed/missing numeric field yields 500 rather than 400.

Acceptance criteria

• POST /v1/streams with non-numeric ratePerSecond or depositedAmount returns 400 with a validation error
• POST /v1/streams with a missing required numeric field returns 400, not 500
• Numeric coercion happens after presence/format validation (or is wrapped so any conversion failure maps to 400)

Files to touch

• backend/src/controllers/stream.controller.ts

Out of scope

• Stellar address format validation (tracked separately)

[Tobi-8]

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

hey, i reviewed your description and it is something i can comfortably do, i'd appreciate if you gave me the opportunity of getting this issue

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

[BernardOnuh]

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

Hi maintainer, I would love to contribute to this issue by applying the necessary fixes and improvements to get it done

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

[Caneryy]

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

Hello! Can I work on this issue please?

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

[drips-wave]

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

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

[grantfox-oss]

🦊 GrantFox — @BernardOnuh has been assigned to this issue!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #810)
2. Your PR will be reviewed by the LabsCrypt maintainers

Good luck! Track your progress on GrantFox.