[Feature]: Notification Service Backend

[SudiptaPaul-31]

🔍 Problem Statement

Description
Implement a backend notification system to handle important group and contract-related events, ensuring real-time delivery and persistent storage.

Events

• Contract creation
• Milestone submission
• Escrow release
• Dispute creation

Requirements

• Store notifications in database with fields: id, userId, eventType, message, timestamp, read
• Support read/unread status updates
• Provide API endpoints to fetch notifications (with pagination and filtering)
• Deliver notifications in real time via WebSocket or push events
• Ensure proper error handling and logging for failed delivery attempts

Tasks

• Define notification schema in database
• Implement notification creation logic triggered by events
• Build API endpoints for fetching and updating notifications
• Integrate WebSocket/push service for real-time delivery
• Add unit tests for notification creation, retrieval, and status updates

Acceptance Criteria

• Notifications stored reliably in database with correct event mapping
• Read/unread status supported and persisted
• Notifications delivered in real time to connected clients
• API endpoints documented for frontend integration
• Pagination supported for large notification lists
• Unit tests pass for backend logic and API endpoints

📈 Expected Impact

High — Would significantly improve user experience

[okeolaolatun23-glitch]

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

I would like to work on this ASAP

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

[Macnelson9]

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

Hi team, I'd like to take on this issue.

I specialize in Rust development, smart contract engineering, and frontend development with Next.js, React, and TypeScript. My experience allows me to bridge on-chain functionality with intuitive user experiences, ensuring both technical correctness and usability.

I'll follow the existing codebase conventions, communicate progress clearly, and deliver a high-quality solution within the expected timeline.

Thank you for your consideration.

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

[patopatrish]

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

Hello maintainer, i would love to work ont this issue.

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

[deslawson]

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

I can handle this issue

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

[iyanumajekodunmi756]

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

I would love to work on this issue

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

[drips-wave]

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

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