Restructure `config.ts` into a per-network config map

[Miracle656]

Background

src/config.ts builds a single frozen config object at import — one Horizon, one RPC, one passphrase, one Soroswap factory. Worse, the defaults are incoherent: HORIZON_URL/RPC_URL default to testnet while the Soroswap factory, Reflector oracle and Aquarius API default to mainnet addresses. Dual-network needs config resolved per network, not one flat object.

What to build

Replace the flat config with config.networks.{testnet,mainnet}, each carrying horizon.url, rpc.url, network.passphrase, soroswap.factoryAddress, oracle ids, and watched pairs — from paired env vars.

Key files

• src/config.ts (31-72)

Suggested execution

git checkout -b feat/per-network-config

1. Read paired env: HORIZON_URL_{TESTNET,MAINNET}, RPC_URL_*, NETWORK_PASSPHRASE_*, SOROSWAP_FACTORY_ADDRESS_*, REFLECTOR_CONTRACT_ID_*, WATCHED_PAIRS_*
2. Expose getNetworkConfig(network); keep single-var fallback
3. Update .env.example with both networks

Acceptance criteria

• config.networks.testnet and .mainnet each fully specified
• No more incoherent testnet-RPC/mainnet-contract defaults
• Back-compat single-network env still resolves
• .env.example documents both

Drips Wave · Complexity: Advanced · 200 points

---

Required: Before submitting, join the contributor Telegram so your work can be tracked and counted toward the Stellar Wave: https://t.me/+fxHXq8f1SwlkZDBk

[Amas-01]

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

Hello Maintainer, I'll like to work on this. Please Assign me

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

[gideonpius7-design]

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

I would like to apply for this issue to refactor src/config.ts into a clean, multi-network config structure. Resolving per-network configurations will fix the current mismatch between default testnet RPCs and mainnet contract addresses while preserving backwards compatibility.

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

[drips-wave]

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

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