Navbar passes hardcoded userId="user-1" to NavRankBadge and CreditBalance

[Benjtalkshow]

components/global-navbar.tsx:143-144 and components/ui/global-resizable-navbar.tsx:40 both pass userId="user-1" to <NavRankBadge> and <CreditBalance>. Every authenticated user sees user-1's rank and credit balance in the navbar regardless of who they're signed in as.

A {/* TODO: Replace with actual auth user ID */} comment is already there acknowledging the placeholder.

What to do

In both files:

• Read the session via authClient.useSession() (already imported in global-navbar.tsx, needs adding in global-resizable-navbar.tsx)
• Pull userId = session?.user?.id
• Pass that to both NavRankBadge and CreditBalance. When undefined, the components already render their own empty state.

Remove the TODO comment once wired.

Acceptance criteria

• Signed-in users see their own rank badge and credit balance in the navbar
• Signed-out users see whatever empty state NavRankBadge and CreditBalance already render for undefined userId
• No grep hit for "user-1" in either navbar file
• TODO comment removed

Files

• components/global-navbar.tsx
• components/ui/global-resizable-navbar.tsx

[linear]

BOU-294

[Jo-anny]

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

Hi, I would love to work on this issue.

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

[coderabbitai]

🔗 Related PRs

#62 - feat: introduce leaderboard page with filtering, table, and user rank [merged]
#63 - feat: Add mini-leaderboard and user rank badge components [merged]
#76 - Wallet page [merged]
#190 - fix: highlight current user on leaderboard and fix profile route [merged]
#198 - feat: Feature: Profile Settings / Edit Profile [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!

[leocagli]

Hi, I'd like to fix this. The approach: read the authenticated user's ID from the auth session (same pattern as the reverted PR #190) and thread it through to NavRankBadge and CreditBalance in both navbar components. Single-file change, no new deps. Could you assign me?

[olalois]

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

Hello Maintainer,
I’ll love to work on this issue, I’m comfortable with auth flows and will correctly wire session-based user IDs into the navbar so each user sees their own data, removing hardcoded values cleanly.

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

[DatboiCaleb]

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

Hi Good day Maintainer

I’m a smart contract and full-stack developer who turns complex ideas into secure, production-ready blockchain code. With strong skills in Rust and Solidity, I build systems that are fast, safe, and built to last.
My experience with the Stellar SDK and Soroban lets me ship real-world Web3 solutions that actually move value.

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

[Codekill33]

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

Hi! I’d like to work on this issue. I’ll update both navbar components to use authClient.useSession() to retrieve the authenticated user’s ID, pass it to NavRankBadge and CreditBalance, remove the hardcoded userId="user-1" and the TODO comment, and verify that signed-in users see their own data while signed-out users receive the existing empty state.

ETA: 1 hour

Kindly assign this issue to me. Thank you!

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