Implement WebSocket Gateway

[RUKAYAT-CODER]

Overview

Add real-time communication via WebSockets for live updates and notifications.

Background

REST API provides request-response but users need real-time updates for quest status, submissions, and payouts.

Specifications

Events to Stream:

• New quest notifications
• Submission status updates
• Payout confirmations
• Live chat support
• Real-time analytics
• Quest deadline alerts
• Reputation changes

Tasks:

• Configure WebSocket gateway
• Create event channels
• Implement authentication
• Build subscription management
• Add message persistence
• Create reconnection logic
• Implement rate limiting for WS
• Add broadcast capabilities

Impacted Files:

• src/modules/websocket/websocket.gateway.ts (new)
• src/modules/websocket/websocket.module.ts (new)
• src/modules/websocket/entities/ws-subscription.entity.ts (new)
• src/common/guards/ws-auth.guard.ts (new)
• src/events/handlers/websocket-event.handlers.ts (new)

Labels: backend, websocket, real-time, streaming, notifications

Acceptance Criteria

• WebSocket connections established
• Authentication works
• Clients can subscribe to channels
• Events pushed in real-time
• Reconnection handled
• Rate limiting prevents abuse
• Broadcast to groups works
• Message history available

🙌Contribution Guidelines:

Assignment required before PR submission
Timeframe: 96-120 hours
Create a screenshot of your implementation/s or sever running
PR description must include: Close #[issue-number]
Star the repo⭐
For more context, please refer to the backend README 🚀

[steph-crown]

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

I'll biild the WebSocket gateway, implement event channels for quest updates/payouts, and add reconnection logic with rbte limiting.

Relevant experience

• I've built WebSocket gateways for high-traffic platforms which handless live notifications and chat with message persistence.

I also have experience implementing WS-specific guards and subscription management to ensure authenticated data broadcasting.

Can I work on this issue?

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

[Stephan-Thomas]

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

hi, i would like to work on this.

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

[drips-wave]

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

🧑‍💻 @steph-crown: 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 @steph-crown as part of the Stellar Wave Program's 3rd Wave 🥳

😎 @steph-crown: 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.