Frontend: Add notifications for events

[Smartdevs17]

Problem

Users don't get notified of important events.

Proposed Solution

Add toast notifications for events.

Acceptance Criteria

• Notify on transaction confirmed
• Notify on project status change
• Notify on new invoice
• Allow enabling/disabling

Technical Notes

• Files: frontend/components/providers.tsx
• Use existing sonner library

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 150 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[KingDavid9999]

@KingDavid9999 has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

I have extensive experience implementing toast notification systems in React applications, including working with the Sonner library specifically, which is already in this project's stack, meaning I can hit the ground running without a learning curve on the tooling, and can integrate notification calls cleanly into the existing providers.tsx architecture without introducing unnecessary dependencies or architectural drift. I've built event-driven notification layers before, wiring toast triggers to async lifecycle events such as transaction confirmations, status changes, and incoming data events, which maps directly to the three core notification triggers required here, transaction confirmed, project status change, and new invoice, and I understand how to structure these so that each event type has a distinct, descriptive message that gives the user actionable context rather than a generic alert. I'm experienced in managing notification preferences at the provider level, implementing enable/disable toggles that persist user preferences either in local state, localStorage, or a user settings context, ensuring that users who opt out of notifications are never interrupted while users who opt in receive timely, non-intrusive feedback. I also understand the importance of notification UX subtleties in a payments and invoicing context, such as distinguishing success, warning, and error toasts with appropriate styling and duration, avoiding notification spam when multiple events fire in quick succession, and ensuring toasts are accessible with proper ARIA live region support, all of which I would factor into the implementation to deliver a polished, production-ready notification system that genuinely improves the user experience across the platform.

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

[drips-wave]

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

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