feat: Save and import custom network profiles with passphrase verification

[dotunv]

Overview

Add the ability to save and import custom Horizon server configurations (name, base URL, network passphrase, friendbot URL) so users can target alternate networks (public, testnet, futurenet, or a custom/private chain) without re-entering settings each session.

Motivation

Users switch between public, testnet, futurenet, and private/custom Stellar networks. Today there's no way to save a named network profile, so users must reconfigure the network each time, and there's no validation that a chosen Horizon URL matches the expected network passphrase, which can silently cause confusing failures.

Proposed Design

1. Add a network_profiles table: id, owner_id, name, horizon_url, network_passphrase, friendbot_url (optional), is_default
2. Add CRUD endpoints and a UI (Network Status / Settings) to manage named profiles
3. When setting a Horizon URL, verify it by fetching the network passphrase and comparing to the selected/expected one; warn on mismatch
4. Allow marking one profile as default used on startup
5. Add import/export of a profile as JSON for sharing within a team
6. Store profiles per user (private by default, no cross-user sharing without an explicit share flag)

Acceptance Criteria

• Users can create, list, update, delete named network profiles
• Profile includes horizon_url, network_passphrase, optional friendbot_url, and default flag
• Selecting a profile configures the active network across tools
• A passphrase mismatch between the fetched Horizon and the selected profile produces a clear warning
• Users can mark one profile as default
• Profiles can be exported/imported as JSON
• Profiles are private to the user unless explicitly shared
• Tests cover: CRUD, passphrase mismatch detection, default handling, import/export, authorization

[Jo-anny]

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

Hi, I would love to work on this issue.

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

[Vivianndev]

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

Hii, I'd love the opportunity to resolve this mean. Please assign to me

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

[Obetaebube3]

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

Hello, I would love to take on this issue. I'm a software engineer with over 4 years experience. and i'm confident I can resolve this issue

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

[felladaniel36-hash]

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

can i please work on this ?

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

[drips-wave]

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

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