Network indicator + wrong-network detection

[truthixify]

Tier: S (½-1 day) Type: feature

Context

good-first-issue

Scope

Wallet network mismatches break the app silently. Show the current network in the header and warn loudly when wallet is on the wrong network.

Acceptance criteria

• Header badge: chain + network ("Stellar Testnet", green for correct, yellow/red for mismatch)
• Sticky banner when wallet ≠ expected network with switch instructions
• Disable Send/Receive/Withdraw buttons during mismatch
• Mainnet warning if wallet on mainnet but app on testnet

Files to start with

• Network badge visible across all pages
• Mismatch banner with action button
• Reactive on wallet network change
• Mainnet warning louder than testnet mismatch
• Playwright test for the mismatch flow

Why this matters

• src/components/Header.tsx
• src/context/StellarWalletContext.tsx
• src/config.ts

[clintjeff2]

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

Hello, I have 6 years of experience working on tasks like this and handling similar challenges across backend, frontend, and smart-contract development. I have carefully read and fully understood the task requirements, and I am confident I can deliver a clean, efficient, and well-tested solution promptly. I always ensure high-quality implementation, maintainability, and adherence to best practices.

Pull request in 5 hours.

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

[bl4vk-0bsidi4n]

@bl4vk-0bsidi4n has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hello Maintainer,
Please I'd love to work on this issue.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @bl4vk-0bsidi4n to this issue.

[drips-wave]

Congratulations, @bl4vk-0bsidi4n! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @bl4vk-0bsidi4n: 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 🌊

[truthixify]

@bl4vk-0bsidi4n Assigned. Welcome to wave 6.

Quick expectations to make this smooth for both sides:

1. Branch from develop (not main). PRs target develop.
2. Open a draft PR within ~3 days of pickup so we can see direction early.
3. Update at least every 5 days. If you get stuck or context changes, just say so on the PR — silence is the only thing that costs you the assignment.
4. Read the issue body's acceptance criteria carefully. Hitting those is the merge bar.

If anything is ambiguous, ask before building. Looking forward to the PR.

[truthixify]

Resolved by #81 (merged into develop).

[drips-wave]

This issue has been completed by @bl4vk-0bsidi4n as part of the Stellar Wave Program's 6th Wave 🥳

😎 @bl4vk-0bsidi4n: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

[truthixify]

Reopening — closed in error. PR #81 resolves #62 (stealth vault UI), not this one.