Bug: TokenSelector.tsx's Stellar address regex accepts invalid characters, and the component has zero test coverage

[Jaydbrown]

Location

components/TokenSelector.tsx:35 (regex); component-wide (test coverage)

Description

Two related gaps in the same file:

1. The address-validation regex /^[GC][A-Z0-9]{55}$/ accepts characters (0, 1, 8, 9) that can never appear in a valid Stellar StrKey address (base32, RFC4648 alphabet A-Z2-7), deferring the real error to a much worse network-level failure message. It also accepts a G-prefixed (account) address for a field that, per its purpose (selecting a token contract), should only accept C-prefixed (contract) addresses.
2. This component has real async data-fetching, abort-handling, and error-branching logic, but no corresponding test file at all, unlike most comparable components in components/stream/.

Why it matters

Users get a confusing late-stage RPC error instead of immediate client-side validation feedback, and could paste an account address into a token-contract field with no warning. The complete lack of tests is exactly why this regex bug went unnoticed.

Suggested fix

Fix the regex to /^C[A-Z2-7]{55}$/ (contract addresses only, correct alphabet), or use the Stellar SDK's own StrKey validation helpers. Add components/TokenSelector.test.tsx covering valid/invalid address input, loading state, abort/cancellation on rapid re-selection, error display, and a regression test for this exact regex bug.

Acceptance criteria

• Regex only accepts the valid base32 alphabet, scoped to contract (C...) addresses
• TokenSelector.test.tsx exists with meaningful coverage of the async/validation/error paths, including a regression test for the regex fix

[rexx010]

Hi, I’m interested in working on this issue. I’ve worked on frontend validation and async state handling before, so I’d tighten the address validation to accept only valid C... contract addresses and the correct Stellar base32 alphabet, then add meaningful tests for validation, loading, cancellation, and error states, including a regression test for the current regex bug.

[Joyyyb]

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

Hi, Maintainer. I would like to work on this issue

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

[drips-wave]

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

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