[Frontend] Stream detail EVENT_STYLES doesn't cover FEE_CONFIG_UPDATED / ADMIN_TRANSFERRED

[ogazboiz]

Join the discussion on Telegram

Why this matters

frontend/src/app/streams/[id]/page.tsx lines 57-66 defines styles for 8 event types but the backend now indexes 10:

The page handles: CREATED, TOPPED_UP, WITHDRAWN, CANCELLED, COMPLETED, PAUSED, RESUMED, FEE_COLLECTED.

But backend/src/controllers/stream.controller.ts:297 and the worker handle two more: FEE_CONFIG_UPDATED and ADMIN_TRANSFERRED. Those land in the events table tied to the system stream (#0), but if any real stream ever ends up with one (or the page later joins them in), they render with the default placeholder •/grey style.

Cosmetic but reflects the broader event union completed in #576 (which covered missing FEE_COLLECTED in the StreamEventType union).

Acceptance criteria

• Add entries for FEE_CONFIG_UPDATED and ADMIN_TRANSFERRED to EVENT_STYLES
• Pick a sensible color/icon pair (suggestion: slate / 'cfg' / 'admin' label)
• No layout change

Files to touch

• frontend/src/app/streams/[id]/page.tsx (lines 57-66)

Out of scope

• Filtering admin events out of public stream views

[RaymondAbiola]

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

Hi, I’d like to work on this issue. I have experience with rust, Solidity, frontend, and backend development, and I’m confident I can deliver a clean solution.

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

[T-kesh]

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

I would like to work on this

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

[N-i-xx]

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

Dear maintainer
Please assign me this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @N-i-xx to this issue.

[drips-wave]

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

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