Wire NotificationDropdown to live SSE events with unread count badge

[ogazboiz]

Join our community: https://t.me/+DOylgFv1jyJlNzM0

Description

NotificationDropdown currently polls fetchUserEvents() only when the dropdown opens. There is no live unread count badge — users have no way to know events happened without opening the dropdown.

What Needs to Happen

• Use useStreamEvents({ userPublicKeys: [publicKey] }) to receive real-time events
• Maintain an unread count in local state; increment on each incoming event while dropdown is closed
• Show the unread count badge on the bell icon (red dot with number)
• Clear unread count when dropdown opens
• Prepend live events to the notification list (max 20, newest first)
• Handle all event types including PAUSED and RESUMED

Files

• frontend/src/components/NotificationDropdown.tsx

Acceptance Criteria

• Unread badge updates in real-time without opening dropdown
• PAUSED and RESUMED events produce notifications
• Badge cleared when dropdown opens

[Arome8240]

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

Hello, I'm a smart contract and full stack developer, open for contributions. contributed to over 20 project on OnlyDust and Drips , with expertise in Solidity, Cairo, JavaScript, TypeScript, and RUST. I am passionate about building secure and scalable blockchain solutions, and I would love the opportunity to contribute my skills toward solving this issue.

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

[olawale880]

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

please can i work on the issue

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

[Treasure332]

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

please can i work on the issue

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

[Christopherdominic]

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

Can I work on this issue

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

[drips-wave]

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

🧑‍💻 @Christopherdominic: 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 @Christopherdominic as part of the Stellar Wave Program's 4th Wave 🥳

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