Repository navigation
Add environment constants (sandbox/production, testnet/mainnet) #3
Description
Description:
The SDK targets two environments — sandbox (Stellar testnet, staging backend) and production (Stellar mainnet, live backend). These must be represented as an enum so the HTTP client and Stellar layer automatically resolve the correct API base URL and network passphrase without the user doing the mapping themselves.
Proposed Steps:
- Define an
Environmentenum inconfig.pywith valuesSANDBOXandPRODUCTION. - Map each value to its Horizon URL, network passphrase, and Shade backend URL.
- Accept string shorthands
"sandbox"/"production"via aparse_environment()coercer. - Default the SDK to
SANDBOXso developers don't accidentally hit production.
Acceptance Criteria:
-
shade.environment = "production"resolves to the mainnet Horizon URL and production API base. -
shade.environment = "sandbox"resolves to the testnet Horizon URL and staging API base. - Invalid strings raise
ValueErrorwith the list of valid options. - The Stellar layer reads
Environmentwithout separate configuration.
Activity
123xiaode456-boop commentedon Jun 22, 2026
/attempt #22
Dannyorji commentedon Jun 28, 2026
HI Maintainer
I will like to take this on.
Please assign
Thanks
grantfox-oss commentedon Jun 28, 2026
🦊 GrantFox — @Dannyorji has been assigned to this issue as part of the Official Campaign campaign!
Next steps:
Closes #3)Good luck! Track your progress on GrantFox.
grantfox-oss commentedon Jun 29, 2026
🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign campaign!
@Dannyorji's PR #33 was approved and merged by @codebestia.
🏆 @Dannyorji: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (118 total points). Track your full progress on GrantFox.
👏 Great work, @Dannyorji! Keep contributing to ShadeProtocol.