WebSocket or SSE: push stream status updates to clients

[greatest0fallt1me]

Description

Real-time channel (SSE or WebSocket) notifying subscribers when stream status or balance snapshot changes.

Requirements and context

• Auth for subscription.
• Backpressure strategy documented.

Suggested execution

• Fork the repository and create a branch (example below).
• Implement changes in StreamPay-Backend (TypeScript / Express per package.json).
• Keep the service secure, tested, and documented; prefer small, reviewable PRs.

git checkout -b feature/sse-stream-updates

Implementation targets

• src/routes/sse/streams.ts or ws server.
• Pub/sub from ingestion service.

Tests and validation

• Tests: connection lifecycle with mock events.

• Run npm test and npm run lint in StreamPay-Backend.

• Cover edge cases; include test output and brief security notes in the PR description.

Guidelines

• Target minimum 95% test coverage on new or changed backend code (or justify gaps).
• Clear documentation (OpenAPI / README / inline docs as specified).
• Timeframe: 96 hours from assignment.

Example commit message

feat(backend): real-time stream update channel

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 200 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[Muyideen-js]

@Muyideen-js has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

I can implement a real-time update channel using SSE or WebSocket to notify clients when stream status or balance snapshots change. The solution will include authenticated subscriptions, a documented backpressure strategy, and a pub/sub connection from the ingestion service. I will add tests covering the connection lifecycle with mock events, ensure ≥95% test coverage, and run npm test and npm run lint. Documentation and security notes will also be included in the PR.

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

[drips-wave]

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

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