[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

Labels: bug, frontend, Stellar Wave

The dashboard refetches its whole snapshot once per SSE event, with no debounce and no cancellation, so a burst of events turns into a refetch storm and can commit stale data.

frontend/src/components/dashboard/dashboard-view.tsx:454-468: the effect deps are [streamEvents, session.publicKey], and streamEvents is a new array on every SSE event, so the effect runs fetchDashboardData (two fetches) every time. Nothing debounces it and there's no AbortController, so overlapping responses can resolve out of order and setSnapshot ends up writing older data on top of newer.

What the fix has to hold to

• SSE-driven refetches are coalesced/debounced (or the effect only reacts to the latest event id)
• The previous in-flight fetchDashboardData is aborted before a new one starts, and stale resolutions are ignored

Done when

• Refetches debounced/coalesced
• Previous fetch cancelled via AbortController, stale results dropped
• lint + typecheck + tests green

Where to start
dashboard-view.tsx and lib/dashboard.ts. Moving dashboard data onto react-query with a typed key would give you dedupe and cancellation for free and is worth considering, but the minimal fix is debounce + abort. The duplicate fetchDashboardData on mount is a separate issue, not this one.

[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 🌊