Add Wallet Route Guards for Member Screens

[Lakes41]

Difficulty: Hard

Type: Bug

Summary

Add consistent wallet connection guards to screens that require a connected wallet so users cannot directly open member-only routes in an invalid state.

Current Behaviour

The root route redirects disconnected users to onboarding, but routes such as /guilds, /guilds/[guildId], and /settings can still be opened directly through navigation, deep links, or reload-like flows. Some of these screens assume wallet state or show member functionality even when no wallet is connected.

Expected Behaviour

Screens that require a connected wallet should show a clear wallet-required state or redirect users to the profile/onboarding flow before running wallet-scoped queries or showing member-only data.

Suggested Implementation

Create a reusable route guard or screen wrapper, such as WalletRequired, that reads the wallet store and either renders children, redirects to /profile, or shows a connect-wallet empty state. Apply it to guild list, guild detail, settings account actions, and any future wallet-scoped screens. Keep access check usable for manual verification if that is intended, but make the wallet requirement explicit where needed.

Files or Areas Likely Affected

• app/guilds.tsx
• app/guilds/[guildId].tsx
• app/settings.tsx
• app/profile.tsx
• src/features/wallet/
• src/components/

Acceptance Criteria

• Disconnected users cannot access guild detail data accidentally.
• Wallet-required screens render a clear connect-wallet state or redirect.
• Wallet-scoped queries do not run when walletAddress is missing.
• Deep links into wallet-required screens handle missing wallet state safely.
• Tests cover connected and disconnected route states.

Additional Notes

Assumption: /access-check may remain usable without a connected wallet because it supports manual wallet entry. Confirm this behaviour before applying the guard to access checks.

[clintjeff2]

Hello, I have 6 years of experience working on tasks like this and handling similar challenges across backend, frontend, and smart-contract development. I have carefully read and fully understood the task requirements, and I am confident I can deliver a clean, efficient, and well-tested solution promptly. I always ensure high-quality implementation, maintainability, and adherence to best practices.

Pull request in 10 hours

[GBOYEE]

Hey! I can work on this. I will add a RequireWallet guard component that gates wallet-dependent routes and redirects disconnected users to onboarding. PR incoming shortly.

[gloskull]

Hi, I’d love to work on this issue. I have 4 years of experience across backend, frontend, full-stack, and smart contract development. I understand the task clearly and can deliver a clean, efficient, well-tested solution on time, with strong focus on code quality and maintainability. My PR will be submitted in under 10 hours.

[grantfox-oss]

🦊 GrantFox — @GBOYEE 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 #49)
2. Your PR will be reviewed by the Adamantine-guild maintainers

Good luck! Track your progress on GrantFox.

[GBOYEE]

PR #61 adds the WalletRequired route guard for wallet-scoped screens. This resolves the issue — can close. Thanks!