[Backend] Add Notification Deduplication Mechanism

[Abd-Standard]

Description

Prevent duplicate notifications from being processed multiple times.

Tasks
Define deduplication strategy.
Generate unique identifiers.
Add duplicate detection.
Log duplicate events.

Acceptance Criteria
Duplicate notifications are detected.
Legitimate notifications are unaffected.
Detection remains performant.

[ekwe7]

I would love to work on this issue. I have experience building production ready applications and collaborating through GitHub workflows. I'll carefully analyze the current implementation, propose a reliable solution, and submit a well-tested PR. My focus is on clean code, maintainability, and timely delivery

[umohjosephemmanuel-cyber]

Enhanced notification processing reliability by implementing a scalable deduplication system with unique event identification, efficient duplicate detection, and comprehensive logging to prevent redundant processing while preserving the integrity of valid notifications.

[Sparexonzy95]

Hi Abd-Standard,

I’d like to work on this issue. I understand the problem: in an event-driven notification system, the same event can be picked up more than once because of polling overlaps, retries, or RPC inconsistencies. Without deduplication, users may receive duplicate notifications and the event history becomes unreliable.

My approach would be to define a stable notification fingerprint using fields such as contract address, event ID, transaction/ledger reference, event type, and recipient where applicable. I would add duplicate detection before notification delivery, ensure legitimate distinct notifications are not blocked, and log skipped duplicates with useful context for auditing.

I would also include tests for duplicate detection, valid unique notifications, fingerprint consistency, and performant lookup behavior.

My goal is to deliver a clean backend PR that makes notification processing idempotent, reliable, and easy to maintain.

[Belzabeem]

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

I have experience implementing backend notification deduplication using unique identifier generation, idempotency key storage, and performant duplicate detection with structured logging for deduplicated events — and I'm ready to apply that pattern to Notify-Chain without impacting legitimate notification throughput.

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

[Babigdk]

I'd like to work on this task. As a software engineer experienced with backend systems, event processing, and reliability improvements, I can implement a robust notification deduplication mechanism.

I will define a clear deduplication strategy, generate consistent unique identifiers for notification events, add duplicate detection logic, and introduce structured logging for skipped duplicates. The implementation will ensure legitimate notifications continue processing while maintaining efficient performance.

The PR will include the deduplication logic, tests covering duplicate and valid notification flows, logging improvements, and validation results.

[akinboyewaSamson]

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

[michaelvic123]

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

please assign this issue to me

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

[drips-wave]

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

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

[grantfox-oss]

🦊 GrantFox — @michaelvic123 has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #259)
2. Your PR will be reviewed by the Core-Foundry maintainers

Good luck! Track your progress on GrantFox.