Per-network SAC / NFT watch-lists via env

[Miracle656]

Background

SAC_CONTRACT_IDS / NFT_CONTRACT_IDS are read once from single env vars, and the default native-XLM SAC differs per network (CDLZFC3SY… mainnet vs CDMLFMKM… testnet). A dual-network build needs each network's watch-list supplied independently.

What to build

Support paired env vars and select the right list per network.

Key files

• src/indexer.ts — resolveSacContractIds() / resolveNftContractIds() (51-88)
• .env.example — document the paired vars

Suggested execution

git checkout -b feat/per-network-watchlists

1. Read SAC_CONTRACT_IDS_TESTNET / _MAINNET (fall back to the single var + the per-network default SAC)
2. Same for NFT_CONTRACT_IDS_*
3. Update .env.example with both networks

Acceptance criteria

• Each network resolves its own watch-list + default SAC
• Falls back to legacy single-var behaviour
• .env.example documents both

Drips Wave · Complexity: Easy · 100 points

---

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

[kenzy-hue]

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

Hello Maintainer, I’d love to work on this project. I’m a professional, experienced, and confident in my ability to contribute high-quality work. I’m ready to bring my skills, consistency, and attention to detail to the project.

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

[tobiadewola41-eng]

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

I would like to work on this issue because

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

[ibochielizabeth-spec]

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

I’m interested in working on Issue #162 because supporting multiple networks requires Wraith to maintain separate SAC and NFT watch-lists instead of relying on a single global environment variable.

I will first review resolveSacContractIds() and resolveNftContractIds() in src/indexer.ts to understand the current resolution and fallback behavior. I will then add support for SAC_CONTRACT_IDS_TESTNET, SAC_CONTRACT_IDS_MAINNET, NFT_CONTRACT_IDS_TESTNET, and NFT_CONTRACT_IDS_MAINNET.

Each network will resolve its own configured watch-list and use the correct default native XLM SAC when no explicit SAC list is provided. I will preserve the existing single-variable environment configuration as a fallback so current deployments are not unnecessarily broken.

I will also update .env.example with clear documentation for the new per-network variables and their expected usage.

Finally, I will test testnet and mainnet resolution independently, including configured values and fallback scenarios, to confirm that each network receives the correct contracts without affecting the other.

The goal is a simple, backward-compatible configuration that allows Wraith to safely index SAC and NFT contracts across multiple Stellar networks.

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