[Frontend] Dashboard maps every stream to token 'TOKEN' and never reflects Paused/Cancelled status

[ogazboiz]

Telegram: https://t.me/+DOylgFv1jyJlNzM0

Why this matters

mapBackendStreamToFrontend in frontend/src/lib/dashboard.ts has two display bugs feeding the dashboard:

1. token: "TOKEN" is hardcoded, so the dashboard table/cards literally show "TOKEN" instead of XLM/USDC/EURC (the symbol can be resolved from tokenAddress via TOKEN_ADDRESSES, as lib/api/streams.ts already does with resolveTokenLabel).
2. status: s.isActive ? "Active" : "Completed" never produces "Paused" or "Cancelled", even though those are valid Stream["status"] values and BackendStream carries isPaused. As a result the dashboard's Paused tab (which filters s.status === "Paused") is always empty, and cancelled streams show as "Completed".

Acceptance criteria

• Resolve the real token label from tokenAddress
• Map status to Paused (when isPaused), Cancelled/Completed (when inactive — use events or available flags), and Active otherwise
• Dashboard Paused tab shows paused streams; token column shows real symbols

Files to touch

• frontend/src/lib/dashboard.ts (mapBackendStreamToFrontend)

Out of scope

• The incoming-streams mapper in lib/api/streams.ts (already resolves token + status).

[Clement-coder]

@Clement-coder has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Hi, I’m a Full-Stack Software & Blockchain Engineer with experience building React dashboards and blockchain data-mapping layers.

I’d like to take on this issue. I can fix the dashboard stream mapper to resolve actual token symbols from tokenAddress, correctly surface Active, Paused, Cancelled, and Completed states, and ensure the dashboard tabs and status filters reflect real backend stream data.

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

[Heazzy500]

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

I would like to work on this issue

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

[dmystical-coder]

@dmystical-coder has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

I would like to work on this issue. Kindly assign

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

[0xElyte]

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

I would love to resolve this

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

[drips-wave]

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

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