Feature: Profile Settings / Edit Profile

[Benjtalkshow]

Overview

The profile page at app/profile/[userId]/page.tsx is read-only. There is no way for users to edit their own profile, change avatar, update bio, or configure notification preferences. Add a /settings route where authenticated users can manage their own data.

---

Goals

• Allow authenticated users to edit name, bio, avatar URL, and social links
• Allow users to set notification preferences (in-app vs. email, frequency)
• Allow users to disconnect their wallet (with a confirmation dialog)
• Surface validation errors inline

---

Implementation Details

1. Settings route and tabs

Create: app/settings/page.tsx

• Tabs: Profile, Notifications, Wallet, Danger Zone
• Server-side guard: redirect to sign-in if unauthenticated
• Pull current user via authClient.useSession() and a useMe() query

2. Profile tab

Create: components/settings/profile-tab.tsx

• Avatar uploader (or URL input)
• Display name, bio (rich text or markdown editor)
• Social links (GitHub, Twitter, personal site)
• Save via useUpdateUserMutation (add to hooks/use-user-mutations.ts)

3. Notifications tab

Create: components/settings/notifications-tab.tsx

• Per-event-type toggles (in-app, email)
• Email digest cadence (off, daily, weekly)
• Persist to backend via mutation

4. Wallet tab

• Show connected wallet address
• "Disconnect Wallet" button with AlertDialog confirmation

5. Danger zone

• "Delete account" button with double-confirm
• Wired to a useDeleteAccountMutation (placeholder if backend not ready)

---

Files Affected

Created

• app/settings/page.tsx
• components/settings/profile-tab.tsx
• components/settings/notifications-tab.tsx
• components/settings/wallet-tab.tsx
• components/settings/danger-zone-tab.tsx
• hooks/use-user-mutations.ts

---

Acceptance Criteria

• /settings is reachable only by authenticated users
• User can update name, bio, avatar, and social links and changes persist
• Notification preferences are saved per-user
• Wallet disconnect requires confirmation
• Form validation errors surface inline (not as toast)

---

Additional Notes

• Optimistic update on save; rollback on error
• Keep this consistent with the existing dialog/form patterns elsewhere in the app

[linear]

BOU-187

[coderabbitai]

🔗 Related PRs

#39 - feat: implement user authentication and session management hooks for sign-out, password changes, and session revocation [closed]
#40 - feat: add user profile mutation hook with Better Auth integration [merged]
#110 - feat: Implement Earnings & Payout Tracking [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[Sendi0011]

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

Gm team, i will like to work on this, i am a frontend/smartcontract developer with experience skill solving issues like this. i am also an active Open source contributor.
ETA: 4 hours

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

[Oluwatos94]

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

Hi maintainer, I have gone through the detailed description, I'm a full stack developer with extensive experience building backend solution coupling with frontend integration. I understand the requirements and as someone who is familiar with the codebase I can confidently implement this issue. I would like to take on this task and resolve accordingly. Looking forward to assignment.

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

[drips-wave]

Congratulations, @Oluwatos94! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on April 29, 2026.

🧑‍💻 @Oluwatos94: 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 🌊

[Benjtalkshow]

@Oluwatos94
Whats the update on this issue?