Add helper for validating Stellar wallet address format before database queries

[Chucks1093]

Summary

Several endpoints accept a wallet address as a path or query param. Each one currently validates separately or not at all. A shared helper that checks a string is a valid Stellar address format should be called at the start of any handler that accepts a wallet address.

Scope

• Add isValidStellarAddress(address: string): boolean helper using the Stellar SDK or a regex for the base32 G-account format
• Use the helper in: GET /wallets/:address/holdings, GET /wallets/:address/activity, POST /alerts
• Return 400 with a descriptive message when validation fails
• Add unit tests for: valid address, address with wrong prefix, too short, too long, empty string

Acceptance Criteria

• Valid Stellar address passes validation
• Invalid formats return 400 with descriptive error
• Helper is used consistently across all wallet address params
• Unit tests cover all invalid cases

ETA: 12 hours

---

Coordinate on Telegram

[mxrtins04]

Hi, can i have this issue please?

[spiffamani]

I'm a full-stack Software Engineer with 3 years of experience
I'd love to take this on — thanks for considering me

[lekanay2005-coder]

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

pls i can solve this issue

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

[Henrichy]

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

Hello Sir,
I came across your project and I’m really interested in contributing.
I have experience with React for building responsive, user-friendly interfaces, and I’m also familiar with smart contracts and blockchain basics. I focus on writing clean, scalable code and improving user experience.
I’m a fast learner and ready to get started immediately. Please let me know the next steps.
Thank you.
Best regards,
Henry

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

[Cjay-Cyber-2]

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

i would like to work on this kindly assign me

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Cjay-Cyber-2 to this issue.

[Jonathan-ai9]

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

Hello,I’d like to work on this issue. I’ll add a shared isValidStellarAddress helper, integrate it into the specified wallet-related endpoints, return descriptive 400 responses for invalid addresses, and add unit tests covering valid and invalid address formats to ensure consistent validation across the API.

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

[pre-cious-Igwealor]

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

Hi, my name is pre-cious-Igwealor, and I am a fullstack and smart contract developer skilled in React, Next.js, JavaScript, TypeScript, Tailwind CSS, and Soroban. For this task, I will:

1. Create a centralized isValidStellarAddress utility function utilizing the Stellar SDK to verify the strict base32 G-account format.
2. Integrate the validation helper into the controllers for GET /wallets/:address/holdings, GET /wallets/:address/activity, and POST /alerts.
3. Configure the middleware layer to instantly reject invalid formats with a 400 Bad Request status and a descriptive error message.
4. Author comprehensive unit tests covering valid addresses, wrong prefixes, incorrect string lengths, and empty inputs to guarantee validation accuracy.

ETA: 10 hours

ℹ️ Repo Maintainers: To accept this application, review their application or assign @pre-cious-Igwealor to this issue.

[grantfox-oss]

🦊 GrantFox — @pre-cious-Igwealor has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

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

Good luck! Track your progress on GrantFox.

[drips-wave]

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

🧑‍💻 @pre-cious-Igwealor: 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 @pre-cious-Igwealor as part of the Stellar Wave Program's 6th Wave 🥳

😎 @pre-cious-Igwealor: 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.