[Frontend] ActivityHistory renderEventMessage doesn't cover FEE_COLLECTED / FEE_CONFIG_UPDATED / ADMIN_TRANSFERRED

[ogazboiz]

Join the discussion on Telegram

Why this matters

frontend/src/components/dashboard/ActivityHistory.tsx lines 62-87 switch on event.eventType for 7 cases (CREATED, TOPPED_UP, WITHDRAWN, CANCELLED, COMPLETED, PAUSED, RESUMED) and falls to a generic Event on Stream #X for everything else.

The backend (backend/src/controllers/stream.controller.ts:297) actually emits 10 event types including FEE_COLLECTED, FEE_CONFIG_UPDATED, ADMIN_TRANSFERRED. Activities of those types currently render uninformatively.

Acceptance criteria

• Add case branches for FEE_COLLECTED, FEE_CONFIG_UPDATED, ADMIN_TRANSFERRED with a human-readable message
• FEE_CONFIG_UPDATED/ADMIN_TRANSFERRED don't have a streamId in the user-facing sense — render without the stream link

Files to touch

• frontend/src/components/dashboard/ActivityHistory.tsx (lines 62-87)

Out of scope

• Hiding admin events from the user view (separate UX decision)

[Kami-no-san]

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

Hi Maintainer, i will like to work on this

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Kami-no-san to this issue.

[fadesany]

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

Hello maintainer, i would like to work on n this issue

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

[drips-wave]

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

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

[drips-wave]

This issue has been marked as completed by a Drips Wave moderator for @fadesany as part of the Stellar Wave Program's 5th Wave 🥳

Moderator's reason: [Auto-assessed] The contributor successfully addressed all points raised in the maintainer's review, and the maintainer explicitly confirmed that the items were 'addressed cleanly' and the PR would be merged once CI passed. Although the PR is still open, the work is complete, verified by the maintainer, and the PR is in a clean, mergeable state.

😎 @fadesany: You earned 150 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

ℹ️ Note: This issue was marked complete via moderation. Points were issued even though the GitHub issue remains open.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox!

@fadesany's PR #733 was approved and merged by @ogazboiz.

🏆 @fadesany: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (35 total points). Track your full progress on GrantFox.

👏 Great work, @fadesany! Keep contributing to LabsCrypt.