#38 Issue 38: [Config] Multi-Network Environment Support

[JerryIdoko]

Description:
The backend needs to seamlessly switch between Stellar Testnet, Futurenet, and Mainnet using environment variables.
Acceptance Criteria:

[ ] Update rpc_url and network_passphrase to be strictly ENV driven.

[ ] Prevent Mainnet DB from connecting to Testnet RPC by validating the genesis hash on startup.
Labels: config, architecture

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 200 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[morelucks]

@morelucks has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Hello,

I’m a smart contract and full-stack developer interested in contributing to this issue. I’m an experienced contributor on OnlyDust and participated in Drips Wave 1, with hands-on experience in Rust, Soroban, Cairo, Solidity, and TypeScript.

I’m passionate about building secure and scalable blockchain solutions, with a strong focus on writing clean, maintainable code. Based on the scope of this issue, I’m confident I can deliver a complete solution within 4-8 hours of assignment.

I would appreciate the opportunity to contribute and help move this forward.

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

[AlAfiz]

@AlAfiz has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Can I work on this issue?

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

[drips-wave]

Congratulations, @AlAfiz! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on February 26, 2026.

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