src/models/user.rs::CreateUserRequest has an optional stellar_address: Option<String> field that is inserted directly into the users table in src/routes/auth.rs::register with zero format checking, unlike src/routes/accounts.rs::validate_stellar_address which does check length/prefix/alphanumeric for the accounts endpoints.
A malformed address stored at registration will silently break any later feature that assumes users.stellar_address is valid. Additionally, CreateUserRequest/LoginRequest don't use the validator crate already listed in Cargo.toml — validation is ad-hoc and duplicated. Reuse validate_stellar_address (or a shared version of it) in register, and consider adopting #[derive(Validate)] consistently.
src/models/user.rs::CreateUserRequesthas an optionalstellar_address: Option<String>field that is inserted directly into theuserstable insrc/routes/auth.rs::registerwith zero format checking, unlikesrc/routes/accounts.rs::validate_stellar_addresswhich does check length/prefix/alphanumeric for the accounts endpoints.A malformed address stored at registration will silently break any later feature that assumes
users.stellar_addressis valid. Additionally,CreateUserRequest/LoginRequestdon't use thevalidatorcrate already listed inCargo.toml— validation is ad-hoc and duplicated. Reusevalidate_stellar_address(or a shared version of it) inregister, and consider adopting#[derive(Validate)]consistently.