🟠 One `VITE_FACTORY_CONTRACT_ID` shared across the network switcher — mainnet/testnet toggle points both networks at the same contract

[Ejirowebfi]

Area: Frontend · frontend/src/config/env.ts, config/stellar.ts, context/NetworkContext.tsx

Description

The UI offers a runtime testnet/mainnet switcher (persisted in localStorage), but
STELLAR_CONFIG.factoryContractId is a single value from VITE_FACTORY_CONTRACT_ID, applied to
whichever network is selected. Switching a testnet-configured build to mainnet makes the app issue
mainnet transactions against a contract ID that either doesn't exist on mainnet (confusing "contract
not found" failures) or — the dangerous case — does exist as an unrelated contract at the same ID,
against which users could be prompted to sign real-XLM transactions. The same applies to
VITE_TOKEN_WASM_HASH. Additionally, the hardcoded mainnet RPC endpoint
https://soroban-mainnet.stellar.org (config/stellar.ts:21) is not an SDF-operated public service
(SDF provides no public mainnet Soroban RPC), so mainnet mode is broken at the transport layer too.
The service-worker cache key derives from the single contract ID, compounding cross-network cache
confusion.

Tasks

• Introduce per-network env vars (VITE_FACTORY_CONTRACT_ID_TESTNET / _MAINNET, same for the
  WASM hash) resolved through NETWORK_CONFIGS, with the misconfiguration screen listing exactly
  which network is missing configuration.
• Disable (with explanation) the network switcher for any network whose contract ID is not
  configured, instead of switching into a broken state.
• Make the mainnet RPC URL a required explicit env var (VITE_SOROBAN_RPC_URL_MAINNET) with
  documentation on choosing a provider, and validate reachability on startup (surfaced, not
  silent).
• Include the active network in the service-worker cache version key alongside its own contract ID.
• Update .env.example, vercel.json env docs, README, and the Vercel deploy button parameters.
• Tests: network switch resolves the correct contract ID; unconfigured network cannot be selected;
  misconfiguration screen names the missing variable.

Acceptance criteria

• Each network resolves its own contract ID, WASM hash, and RPC endpoint, proven by tests.
• It is impossible to end up signing transactions on network A against network B's (or a missing)
  contract ID via the switcher.
• Mainnet mode has an explicitly configured, documented RPC endpoint.

---

Issue 12 of 20 from the codebase audit tracked in ISSUES.md.

[mayborn005]

Hello @maintainer, I’ve gone through the requirements and I’m confident I can implement a proper solution that matches the acceptance criteria. Kindly assign this issue to me. And I will deliver at the shortest possible time.

[YahKazo]

hi team kindly assign me i can work on this issue am a software engineer

[grantfox-oss]

🦊 GrantFox — @YahKazo has been assigned to this issue as part of the Official Campaign | FWC26 campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #1016)
2. Your PR will be reviewed by the Favourorg maintainers

Good luck! Track your progress on GrantFox.