Dashboard SCREENS constant pre-mounts all 5 screens on load causing redundant data fetches

[k-deejah]

Problem

src/screens/Dashboard.tsx defines the screen map as a module-level constant:

const SCREENS: Record<NavSection, React.ReactNode> = {
  wallet: <WalletScreen />,
  account: <AccountScreen />,
  transactions: <TransactionsScreen />,
  soroban: <SorobanScreen />,
  network: <NetworkScreen />,
};

All five screen components are instantiated as JSX elements when this constant is evaluated — at module import time, before Dashboard even mounts. Every screen's useEffect hooks fire immediately: TransactionHistory fetches history, FeeEstimator fetches fees, ClaimableBalanceCard fetches claimable balances, and ContractEventFeed starts polling — all for screens the user has never visited.

Two more problems: (1) since all screens remain mounted permanently, navigating away from a screen does not unmount it — polling intervals and stale subscriptions accumulate for the session lifetime; (2) state (e.g. SorobanPanel's form inputs) persists across navigation trips, which may be surprising to users.

Solution

Replace the static constant with conditional rendering inside Dashboard, so only the active screen mounts:

<main className="flex-1 overflow-y-auto">
  <div className="max-w-[700px] mx-auto px-6 py-8 sm:px-10 sm:py-10">
    {active === "wallet"       && <WalletScreen />}
    {active === "account"      && <AccountScreen />}
    {active === "transactions" && <TransactionsScreen />}
    {active === "soroban"      && <SorobanScreen />}
    {active === "network"      && <NetworkScreen />}
  </div>
</main>

Acceptance Criteria

• Only the currently active screen is mounted in the DOM at any time
• Navigating away from a screen unmounts it and cleans up its effects and intervals
• No data-fetching useEffect fires for screens the user has never visited
• Switching between screens works correctly with no visible flicker
• ContractEventFeed polling interval is cleaned up when SorobanScreen unmounts

---

Note for Contributors: If you're assigned to this issue, write a clear and detailed description for your pull request. Explain what was changed, why it was needed, how it was implemented, and include any relevant testing or screenshots where applicable.

[Chigybillionz]

Hi, I’d love to take this on. I can start right away.

[buki70]

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

Hi Maintainer,
I’d really appreciate the opportunity to work on this issue. Having reviewed the acceptance criteria, I’m confident that I can submit a PR after being assigned.
Please kindly assign this issue to me.
Thank you!

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

[chiemezie1]

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

Hello, I have reviewed the issue and understand what needs to be done.

I would appreciate being assigned to it.

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

[Olamidepy]

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

Kindly assign to this to me

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

[drips-wave]

Congratulations, @Olamidepy! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

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