Turn the network-mismatch warning into a hard submission guard with explicit passphrase handling

[james2177]

Description: networkMismatch in useWalletStore is currently informational only — SwapCard's canSwap and SolvePageClient's canRegister never check it, meaning a user connected to the wrong network can still submit a swap or solver registration. Additionally, signTransaction(xdr, { network: wallet.network ?? undefined }) passes whatever network string Freighter reports, rather than validating it against the app's expected network passphrase before signing.

Problem Statement & Context: Signing and submitting a transaction while connected to the wrong Stellar network (e.g. testnet vs. mainnet) can result in funds being sent on an unintended network, or a transaction being rejected in a confusing way after the user has already gone through the sign flow. The current warning banner in ConnectWalletButton is easy to miss, and nothing actually stops the risky action.

Scope & Acceptance Criteria:

• SwapCard's canSwap and SolvePageClient's canRegister must both be false while networkMismatch is true, with a clear inline explanation (not just the existing small warning text) of why submission is blocked.
• signTransaction calls in useSwapSubmission.ts/useSolverRegistration.ts should explicitly validate wallet.network against EXPECTED_NETWORK (already computed in src/store/wallet.ts) immediately before calling Freighter, as a defense-in-depth check even if the UI guard above is somehow bypassed (e.g. a stale closure).
• Out of scope: automatically switching networks on the user's behalf (not possible via Freighter's API).

Implementation Guidelines:

1. Key files: src/store/wallet.ts (EXPECTED_NETWORK, networkMismatch), src/components/SwapCard.tsx, src/app/solve/SolvePageClient.tsx, src/hooks/useSwapSubmission.ts, src/hooks/useSolverRegistration.ts.
2. This pairs naturally with issue Pr7 swapcard quote api #9's live mismatch detection but can be implemented independently against the mismatch state as it exists today (checked at connect/hydrate time only) — don't block on Pr7 swapcard quote api #9 being done first.
3. Edge cases: the guard must not falsely block a user who has never connected a wallet at all (networkMismatch defaults to false pre-connection, which is correct — verify this isn't accidentally conflated with "connected and correct").
4. Testing: extend src/components/SwapCard.test.tsx and SolvePageClient tests to assert submission is disabled and clearly explained under a mocked networkMismatch: true wallet state; extend useSwapSubmission.test.ts/useSolverRegistration.test.ts for the defense-in-depth check throwing before calling freighterApi.signTransaction.

Definition of Done:

• Code written, tested.
• Acceptance criteria met; verified via test output.
• PR passes CI.
• Reviewed and approved.

Resources: src/store/wallet.ts, docs/wallet-hydration.md

Complexity: High (200 points)

[muizbolaji4]

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

Hi, I’d be glad to handle this issue. Please assign it to me.

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

[Gadflyxx]

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

hi maintainer kindly assign this to me

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

[drips-wave]

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

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