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
Summary
The backend currently uses
MAINNETas a hardcoded Stellar network value in event and contract handling.Problem
This limits deployment flexibility and makes testnet/futurenet deployments error-prone.
Proposed work
TESTNET,MAINNET,FUTURENET)MAINNETusage to use configFiles
src/stellar/events.tssrc/stellar/contract.tssrc/agent/README.mdpackage.jsonor config env docs if neededAcceptance criteria
MAINNETremoved from runtime logicSTELLAR_NETWORK=testnetor similar