Open key product surfaces in read-only mode before wallet connection #281
Description
Summary
The current application shell in frontend/src/App.jsx keeps the user on the landing hero until a wallet is connected. That means leaderboard, recent tips, platform stats, and general product proof are hidden behind authentication.
Why this matters
For buildathon and hackathon judging, the project should be explorable in under a minute. Requiring wallet connection before users can inspect live activity or platform value creates unnecessary friction and weakens first impression.
Proposed work
- Allow unauthenticated access to read-only routes such as live feed, leaderboard, platform stats, and a public profile view.
- Keep only write actions and account-specific views behind wallet authentication.
- Add clear disabled states or inline prompts for actions that require a wallet.
- Update the navigation and route config- Update the navigation and route config- Updather than partially l- Update t Acceptance criteria
- A new visitor can browse live feed, leaderboard, and platform stats without connecting a wallet.
- Send tip, batch tip, token tip, profile management, and privacy/admin actions remain protected.
- Public routes have clear upgrade prompts when a wallet is required to continue.
- Routing tests cover authenticated and unauthenticated behavior.