Skip to content

Make Stellar network selection configurable instead of hardcoding MAINNET #66

@robertocarlous

Description

@robertocarlous

Summary

The backend currently uses MAINNET as a hardcoded Stellar network value in event and contract handling.

Problem

This limits deployment flexibility and makes testnet/futurenet deployments error-prone.

Proposed work

  • Use environment/config values for Stellar network selection
  • Validate network values against supported options (TESTNET, MAINNET, FUTURENET)
  • Refactor any direct MAINNET usage to use config
  • Update docs and env examples

Files

  • src/stellar/events.ts
  • src/stellar/contract.ts
  • src/agent/README.md
  • package.json or config env docs if needed

Acceptance criteria

  • Network is read from config/env in all relevant code
  • Hardcoded MAINNET removed from runtime logic
  • Deployments can run using STELLAR_NETWORK=testnet or similar

Metadata

Metadata

Assignees

Labels

Stellar WaveIssues in the Stellar wave program

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions