#636 Extract notification creation to NotificationHelper

[vic-Gray]

Area: architecture · Effort: S\n\nWhat: Move repeated notification-building logic into a shared helper or factory.\n\nWhy: Duplicated notification logic causes inconsistencies when templates change.\n\nHints:\n- `backend/src/notifications/notifications.service.ts

[dykdee]

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

I would like to work on this issue because moving repeated notification creation into a shared helper will make the code easier to maintain and keep notification templates consistent across the app.

I have experience with backend refactoring, organizing repeated logic into reusable helpers, and making small architecture improvements without changing existing behavior. I can review the notification service, extract the common notification-building logic into a NotificationHelper, update the current usages, and make sure the existing notification flow still works correctly.

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

[ositaemmanuel653-netizen]

@ositaemmanuel653-netizen has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Hi! I’m a full-stack developer with a strong UI background. I’d love to handle this issue and can deliver a clean, reliable solution. Kindly assign it to me.

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

[Neziahtech]

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

Please assign would work it out very fast

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

[Cjay-Cyber-2]

@Cjay-Cyber-2 has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

i would love to get assigned to this task

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Cjay-Cyber-2 to this issue.

[oscar24357]

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

hello maintainer, please i want to work on this issue, can you please assign me to it, thank you.

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

[dotmantissa]

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

Please, assign this issue to me.

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

[Gezziy]

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

i! I’d like to contribute to this issue. I’m a blockchain and backend developer with experience in Solidity, TypeScript, and Node.js, specializing in secure smart contract development and scalable backend systems. I focus on writing reliable, well-structured code and building efficient integrations for blockchain-based applications.

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

[drips-wave]

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

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