#085: End-to-End Network Switch (Testnet ↔ Mainnet)

[Wilfred007]

#85: End-to-End Network Switch (Testnet ↔ Mainnet)

Category: [FRONTEND]
Difficulty: ● MEDIUM
Tags: network, testnet, mainnet, config, soroban, provider

Description

Implement a network switcher that allows developers and org admins to toggle between Stellar Testnet and Mainnet at runtime. All Soroban contract IDs, Horizon URLs, and Stellar RPC endpoints must resolve dynamically from the backend contract registry (issue #78) based on the selected network. Switching networks should clear all cached state and re-initialize wallet context.

Acceptance Criteria

• Network selector available in the admin panel and developer debug page.
• On switch, contract registry re-fetched from backend for the new network.
• Wallet context, cached balances, and socket subscriptions reset on network change.
• Testnet banner displayed prominently when on non-mainnet network.
• Network preference persisted in localStorage; mainnet selected by default on production builds.

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 200 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[vitodotcom]

@vitodotcom has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Hi! I'd like to take this on.

I'm a Software Engineer with hands-on Soroban and Stellar frontend experience. I'll build the network switcher with dynamic contract registry re-fetching, full wallet context and cache reset on switch, a testnet banner, and localStorage persistence defaulting to mainnet in production.

I've handled similar runtime network toggling in Web3 contexts, so all five acceptance criteria are familiar ground. Ready to start!

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

[Godbrand0]

@Godbrand0 has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

hello, my name is thompson and i would like to work on this issue, given my experience building stella dapps, given the description, i would be able to complete the end to end testnet to mainnet switcher.

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

[drips-wave]

Congratulations, @Godbrand0! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on February 26, 2026.

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