Join our community: https://t.me/+DOylgFv1jyJlNzM0
Why this matters
backend/src/validators/user.validator.ts presumably validates request bodies for user-related routes, but if it doesn't check that a publicKey field matches the Stellar G... (56-char, base32) format before hitting the controller/repository layer, malformed keys propagate deeper into the stack where they fail with less clear errors (or worse, get silently stored).
Acceptance criteria
Files to touch
backend/src/validators/user.validator.ts
Out of scope
- Validating publicKey elsewhere in the codebase (tracked separately for other controllers)
- Adding key checksum verification beyond format
Why this matters
backend/src/validators/user.validator.tspresumably validates request bodies for user-related routes, but if it doesn't check that apublicKeyfield matches the StellarG...(56-char, base32) format before hitting the controller/repository layer, malformed keys propagate deeper into the stack where they fail with less clear errors (or worse, get silently stored).Acceptance criteria
StrKey.isValidEd25519PublicKey) to the relevant schemaFiles to touch
backend/src/validators/user.validator.tsOut of scope