[Frontend] Remove commented-out dead code in WalletButton

[ogazboiz]

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

Why this matters

frontend/src/components/wallet/WalletButton.tsx carries leftover commented-out code: the networkLabel const (line ~81) and a block of wallet-chip__name/wallet-chip__network markup (lines ~94-101) are commented out but left in place. Dead commented blocks make the component harder to read and invite confusion about whether the network label is meant to render in the chip.

Acceptance criteria

• Remove the commented-out networkLabel and chip markup, OR restore them intentionally if the network label should show in the connected chip
• Lint passes

Files to touch

• frontend/src/components/wallet/WalletButton.tsx

Out of scope

• The network-mismatch warning in the dropdown (keep it).

[Stephan-Thomas]

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

hi, i would like to work on this.

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

[SharifIbrahimDev]

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

Hi @ogazboiz, I’d like to work on this issue.

I can clean up the dead commented-out code in WalletButton.tsx while preserving the intended component behavior and readability. I’ll review the surrounding logic to determine whether the networkLabel and wallet chip markup were intentionally disabled or are no longer needed, then either remove them cleanly or restore them intentionally with consistent implementation.

I’ll also ensure:

• The component remains functionally unchanged
• The network-mismatch warning logic stays untouched
• Linting and formatting pass successfully after the refactor

I focus on maintaining clean and maintainable React/TypeScript components, especially in shared UI flows like wallet interactions.

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

[drips-wave]

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

🧑‍💻 @SharifIbrahimDev: 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 completed by @SharifIbrahimDev as part of the Stellar Wave Program's 5th Wave 🥳

😎 @SharifIbrahimDev: You earned 200 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. You can also Leave a review to share your experience working on this issue.

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