[STELLAR] Add Stellar account fields and Privy user linking flow

[Obiajulu-gif]

Overview

Extend ChainMove user profiles so Privy-authenticated users can be linked to Stellar account records safely.

Problem

The app currently uses Privy for signup/auth. To support the Stellar roadmap, users need a clean way to associate their ChainMove account with a Stellar public key or account reference without exposing or storing private keys in frontend code.

Expected solution

Add Stellar-related fields to the user model and profile flow, such as:

• stellarPublicKey
• stellarAccountId
• stellarLinkedAt
• stellarNetwork

Update profile syncing logic so a Privy user can later be linked to a Stellar account.

Requirements

• Do not remove Privy.
• Do not store Stellar secret/private keys.
• Validate Stellar public key format before saving.
• Make fields optional so existing users are not broken.
• Add clear documentation for how Privy auth and Stellar accounts fit together.

Files likely involved

• models/User.ts
• lib/auth/privy.ts
• lib/auth/current-user.ts
• profile/account API routes
• dashboard/profile UI components
• README or docs

Acceptance criteria

• User model supports optional Stellar account fields.
• Existing users continue to work.
• Stellar public key validation is added where appropriate.
• Privy remains the authentication layer.
• No private key is stored or exposed.
• Lint and build pass.

Suggested labels

stellar, auth, backend, security

Difficulty

Intermediate

[Glam26]

I'd like to take this issue.

I've worked on authentication and wallet-linking systems where a Web2 identity provider remains the source of authentication while blockchain accounts are linked as optional user attributes. I've also implemented Stellar account validation and secure wallet association flows.

My plan:

• Extend the user model with optional Stellar account fields (stellarPublicKey, stellarAccountId, stellarLinkedAt, stellarNetwork).
• Keep Privy as the sole authentication layer and treat Stellar accounts as linked identities.
• Add proper Stellar public key validation using the Stellar SDK instead of basic string checks.
• Update profile/account APIs and UI flows to support linking and updating Stellar account information.
• Ensure full backward compatibility for existing users and migrations.
• Document the relationship between Privy authentication and Stellar account ownership, including the explicit rule that private keys are never stored.

I've implemented similar account-linking features before and can deliver a clean, security-focused PR quickly.

[kimanicode]

Hey team,
I'd love to jump on this.
I can safely extend the user model and profile flow to support the optional Stellar fields (stellarPublicKey, etc.) while ensuring Privy remains the exclusive auth layer. I'll make sure we enforce strict public key format validation on the backend, ensure zero private key exposure, and leave zero breaking changes for existing profiles. I'll keep the changes scoped tightly to the specified model, auth utils, and profile routes, and I'll make sure to wrap it up with clear architectural docs.

Could you please assign this to me? Thanks

[Marvy247]

I've reviewed the issue description, and I'm confident I can implement all the requested details smoothly.​ Please assign this issue to me! I can have a PR ready for review in a few hours.
Thank You.

[Adamsonoladipupo]

CAN I WORK ON THIS PLEASE?

[libby-coder]

I would like to work on this issue because I have experience extending user models with optional blockchain account fields while keeping existing auth flows intact, and I understand the security boundary that must be maintained Privy handles auth, Stellar public keys are safe to store, private keys never touch the backend. I can add the Stellar fields to the user model with proper
format validation, update the profile sync logic, and document how the two systems fit together without breaking existing users

[grantfox-oss]

🦊 GrantFox — @libby-coder 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 #27)
2. Your PR will be reviewed by the Chainmove maintainers

Good luck! Track your progress on GrantFox.

[grantfox-oss]

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

@libby-coder's PR #53 was approved and merged by @Obiajulu-gif.

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

👏 Great work, @libby-coder! Keep contributing to Chainmove.