[Frontend] Dashboard refetches full snapshot per SSE event with no debounce or cancellation - request storm and out-of-order setSnapshot

[grantfox-oss]

Telegram (ask questions / claim the issue here first): https://t.me/+DOylgFv1jyJlNzM0

Why this matters

frontend/src/components/dashboard/dashboard-view.tsx:454-468 - the effect's deps are [streamEvents, session.publicKey], and streamEvents gets a new array on every SSE event, so it calls fetchDashboardData (two fetches) once per event. There is no debounce and no AbortController, so a burst of events triggers a refetch storm, and overlapping responses can resolve out of order so setSnapshot may commit stale data.

Acceptance criteria

• Debounce/coalesce SSE-driven refetches (or react only to the latest event id)
• Cancel the previous in-flight fetchDashboardData (AbortController) before starting a new one, and ignore stale resolutions
• Consider migrating dashboard data to react-query with a typed key for built-in dedupe/cancellation

Files to touch

• frontend/src/components/dashboard/dashboard-view.tsx
• frontend/src/lib/dashboard.ts

Out of scope

• Duplicate fetchDashboardData on mount

[gracechukwukwerenandum]

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

Please, I will like to work on this issue.

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

[d3v-active]

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

Please assign . you will get a pr today

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

[Caneryy]

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

Hello, I'd like to work on this issue.

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

[drips-wave]

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

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