[Frontend] Stray Token: labeled statement left inside handleWithdraw on stream detail page

[grantfox-oss]

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

Labels: bug, good first issue, frontend, Stellar Wave

There's a stray Token: line inside handleWithdraw that's just leftover junk.

frontend/src/app/streams/[id]/page.tsx:219: right before setWithdrawing(true) there's a bare Token: which is actually a JS labeled statement doing nothing. It's accidental leftover code and the kind of thing lint should be catching.

Done when

• The Token: label is removed from handleWithdraw
• Withdraw still works and toggles the withdrawing state correctly
• Lint passes clean (no unused-label / no-unused-expressions)

Where to start
One line in page.tsx. Don't refactor the withdraw flow, just delete the label. Good first issue.

[Danielobito009]

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

I would love to work on this issue, please assign me to this issue

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

[BigNathan1]

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

Hello maintainer, I would love to resolve this issue within few hours. I am a Full-Stack Dev with contributions to Oss projects. Please assign

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

[alade-dev]

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

I would love to take on this issue. I have experience with the relevant technologies and ecosystem and have previously worked on a similar project. I’ve reviewed the issue details and documentation, and I understand the problem statement and expected outcome. Please assign this task to me.
I’m ready to begin immediately, PR expected soonest

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

[Kaycee276]

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

Kindly assign boss

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

[drips-wave]

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

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

[grantfox-oss]

🦊 GrantFox — @Kaycee276 has been assigned to this issue!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #862)
2. Your PR will be reviewed by the LabsCrypt maintainers

Good luck! Track your progress on GrantFox.