Freighter network mismatch detection — block all contract calls when wrong network is active

[prodbycorne]

Problem

StellarWalletContext connects Freighter and stores the public key, but it never checks which Stellar network Freighter is currently set to. If a user has Freighter pointing at Mainnet (PUBLIC) while the app is configured for TESTNET, any deposit or unlock transaction will be built against the wrong network passphrase and either fail with a cryptographic error or — worse — be silently routed to the wrong network.

Expected Behaviour

After a successful Freighter connection (and on every subsequent page focus), the app reads Freighter's active network and compares it against NEXT_PUBLIC_STELLAR_NETWORK. If they differ, a persistent dismissible banner warns the user and all contract-interaction buttons (Deposit, Unlock, Boost) are disabled until the user switches networks inside Freighter.

Acceptance Criteria

• StellarWalletContext calls freighter.getNetworkDetails() immediately after getAddress() succeeds and stores the result as networkName: string | null
• isNetworkMismatch: boolean is derived and exposed from the context: true when networkName !== NEXT_PUBLIC_STELLAR_NETWORK
• A NetworkMismatchBanner component renders a sticky top alert (Chakra Alert status='warning') with the message "Freighter is set to {networkName}. Switch to {expected} to use SmartDrop."
• document.addEventListener('visibilitychange', ...) re-checks the Freighter network when the tab regains focus so if the user switches network in Freighter and returns, the banner clears automatically within 1 second
• All three action buttons read isNetworkMismatch from context and pass it into their disabled prop
• Unit test mocks freighter.getNetworkDetails returning a mismatched network and asserts the banner text is visible and action buttons are disabled

Relevant Files

• src/context/StellarWalletContext.tsx — add networkName, isNetworkMismatch
• src/components/AppShell/AppShell.tsx — render NetworkMismatchBanner
• src/app/farm/page.tsx — consume isNetworkMismatch to gate buttons
• src/config/index.ts — stellarNetwork for comparison

[Sparexonzy95]

Hi team, I’d like to work on this issue.

I understand this as a wallet-network safety issue. Currently, StellarWalletContext connects to Freighter and stores the user’s public key, but it does not verify whether Freighter is connected to the same Stellar network that SmartDrop is configured to use. This creates a risk where users may attempt Deposit, Unlock, or Boost actions while Freighter is still set to the wrong network, causing failed transactions or unsafe contract-interaction behavior.

My approach will be to implement the fix at the wallet-context level so the network state becomes available across the app, rather than adding isolated checks inside individual components.

I plan to:

1. Update StellarWalletContext to call freighter.getNetworkDetails() after getAddress() succeeds.
2. Store the active Freighter network as networkName.
3. Derive and expose isNetworkMismatch by comparing networkName against NEXT_PUBLIC_STELLAR_NETWORK.
4. Add a visibilitychange listener so the app re-checks Freighter’s network when the user returns to the tab after switching networks.
5. Add a sticky Chakra warning banner that clearly tells the user which network Freighter is currently using and which network SmartDrop expects.
6. Disable all contract-interaction buttons Deposit, Unlock, and Boost while the network mismatch exists.
7. Add unit coverage by mocking freighter.getNetworkDetails() with a mismatched network, then asserting that the warning banner is visible and action buttons are disabled.

This should make the fix centralized, predictable, and safer for all current and future SmartDrop contract actions.

I’ll keep the PR focused, include clear implementation notes, and add screenshots/test results where helpful.

[grantfox-oss]

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

Next steps:

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

Good luck! Track your progress on GrantFox.