BE-09: Notification Engine v2 (Preferences, Channels, Templates)

[Cedarich]

Labels: backend, notifications, wave4
Complexity: 150 points
Branch: feat/be-notifications-v2
Summary
Centralize notifications across email, push, and in-app with user preferences and templated messages.
Tasks

• Create notification preferences model per user and event type.
• Add templating for consistent subject/body/title content.
• Store in-app notifications with pagination.
• Provide “mark as read” and “mark all as read” endpoints.
  Acceptance Criteria
• Preferences reliably enable/disable notifications by type/channel.
• In-app notification list supports pagination and is consistent across clients.
• Templates render deterministically for the same input payload.

---

[Trovic1]

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

hey can i work on this?

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

[drips-wave]

Congratulations, @Trovic1! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on April 29, 2026.

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

[Babigdk]

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

Hi Maintainer,
I’d like to contribute to resolving this issue. I’m a software engineer with strong experience in computer science and believe I can add value here.
Thank you!

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

[drips-wave]

Congratulations, @Babigdk! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on April 29, 2026.

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