[Wallet] Create ConnectWalletDto

[Eniola3321]

Create DTO validation for Stellar wallet connection requests.

[DaddyMord]

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

Hi there, I carefully reviewed the issue details and I’m confident I can deliver a clean and efficient solution.

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

[idrisososanwo]

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

Hi maintainer, I would like to work on this issue

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

[mallison031]

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

I am writing to take on issue #446 to implement the ConnectWalletDto for the clips-backend repository. The wallet connection endpoint is the front door to your application; without strict Data Transfer Object (DTO) validation, malformed public keys or incomplete signature payloads can bypass initial checks, leading to database errors, broken authentication handshakes, or security vulnerabilities. Implementing a bulletproof DTO is exactly the kind of foundational backend work I excel at, and I am ready to execute this.

I specialize in TypeScript, NestJS, and Web3 authentication flows. Here is my precise execution plan to fulfill your requirements:

Strict Stellar Key Validation: I will implement rigorous validation rules (utilizing class-validator) to ensure the incoming publicKey strictly adheres to the Stellar ED25519 format. By enforcing a 56-character length and a specific Base32 Regex pattern starting with 'G', the backend will automatically reject invalid addresses before they ever hit your controller logic.

Signature & Payload Enforcement: A wallet connection is useless without cryptographic proof. I will ensure the DTO explicitly mandates both the signature and the signedMessage (nonce) fields. If a client attempts to connect without proving ownership of the private key, the request will be immediately blocked.

Human-Readable Error States: I will configure the validation decorators to return clean, actionable error messages. Instead of generic 400 Bad Request errors, the frontend will receive precise feedback (e.g., "publicKey must be a valid Stellar address"), drastically speeding up frontend integration and debugging.

I write clean, secure, and highly defensive backend code designed to protect Web3 protocols from edge cases and malformed inputs.

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

[SharifIbrahimDev]

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

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

I have experience building NestJS and TypeScript backends with strong input validation practices. For this task, I’ll create a ConnectWalletDto with appropriate validation rules to ensure Stellar wallet connection requests are type-safe and reject malformed input early. I’ll follow the existing project conventions, add any necessary tests, and keep the implementation focused and maintainable.

I can deliver a clean solution quickly and will ensure the PR includes the required issue reference.

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

[mogbonjubolaolasunkanmi-art]

@mogbonjubolaolasunkanmi-art 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

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

[grantfox-oss]

🦊 GrantFox — @mogbonjubolaolasunkanmi-art 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 #446)
2. Your PR will be reviewed by the ANYTECHS maintainers

Good luck! Track your progress on GrantFox.

[drips-wave]

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

🧑‍💻 @mogbonjubolaolasunkanmi-art: 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]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign campaign!

@mogbonjubolaolasunkanmi-art's PR #506 was approved and merged by @Eniola3321.

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

👏 Great work, @mogbonjubolaolasunkanmi-art! Keep contributing to ANYTECHS.

[drips-wave]

This issue has been completed by @mogbonjubolaolasunkanmi-art as part of the Stellar Wave Program's 6th Wave 🥳

😎 @mogbonjubolaolasunkanmi-art: 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.