Wallet Connection State Persistence Across Page Refresh

[Kingsman-99]

Description

Refreshing the page disconnects the Freighter wallet, forcing users to re-approve the connection on every visit. The last connected wallet's public key should be cached and the connection silently re-established on mount where the user has previously granted permission.

Technical Context

src/hooks/useWallet.ts should call freighter.isConnected() on mount and, if true, skip the approval popup by calling freighter.getPublicKey() directly. The cached public key is stored in sessionStorage (not localStorage) to avoid persisting across closed browser tabs. src/context/WalletContext.tsx (new or existing) exposes connection state app-wide via a React context. src/components/wallet/WalletConnect.tsx reflects the cached state immediately without a loading flash.

Acceptance Criteria

• After granting connection permission, a hard page refresh reconnects the wallet without a new popup
• The connected wallet address is displayed in the navigation bar within 500 ms of page load
• Closing the browser tab clears the cached key from sessionStorage so the next session starts fresh
• If Freighter is not installed, a polite prompt with an install link appears instead of an error
• Disconnecting via the UI clears the sessionStorage entry and renders the connect button
• All CI checks (npm test, npm run build, ESLint/TypeScript) pass and the branch has no merge conflicts

---

[Sensei-Victor]

@Sensei-Victor has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

I’d like to work on this issue because I’m interested in improving wallet connection persistence and ensuring a smoother user experience across page refreshes. I’m comfortable working with frontend state management and can implement and test the required fix.

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

[SYMBAxx]

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

i'd love to resolve this issue for you

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

[drips-wave]

Congratulations, @SYMBAxx! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

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

[drips-wave]

This issue has been completed by @SYMBAxx as part of the Stellar Wave Program's 7th Wave 🥳

😎 @SYMBAxx: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.