Clear distribution session storage on wallet disconnect

[pragmaticAweds]

Context

Distribution form state persists in sessionStorage across wallet switches. When a user disconnects and reconnects with a different wallet, they see the previous wallet's draft distribution data (recipients, amounts, type). This is confusing and could lead to sending tokens to the wrong addresses from the wrong account.

What Success Looks Like

• When a user disconnects their wallet, any persisted distribution form state in sessionStorage is cleared
• Reconnecting with a new wallet starts with a fresh distribution form
• The existing clearPersistedState() method from use-distribution-state.ts is called during disconnect

Implementation Guidance

• apps/web/src/providers/StellarWalletProvider.tsx — the disconnect callback (line 85-91) currently only clears wallet-related localStorage keys
• apps/web/src/hooks/use-distribution-state.ts — has a clearPersistedState() internal function (line ~310) and the key fundable_distribution_state in sessionStorage
• Option A: Import and call the clear function in the disconnect handler
• Option B: Add a useEffect in the distribution hook that watches the wallet address and clears state when it changes to null
• Option B is cleaner as it doesn't couple the wallet provider to the distribution feature

[Trovic1]

@Trovic1 has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

Hi! I’d like to claim this issue for stellar_client_os.
I can implement the session clearing logic using Option B, as it provides better decoupling between the wallet provider and the distribution state. I'll add a useEffect in use-distribution-state.ts to watch the wallet address and ensure sessionStorage is wiped whenever the address becomes null, preventing stale data from leaking across wallet switches.

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

[dinahmaccodes]

@dinahmaccodes has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

GM! I can do this well and do it properly. I am a solid engineer. Can i be assigned this issue?

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

[drips-wave]

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

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