#4. Sync Deployed Contract and Market Manifests Into the Indexer

[IbrahimIjai]

Depends on: Issue 3
Primary outcome: The indexer can discover SO4 contracts, tokens, and markets from deployment outputs instead of hardcoded IDs.

Background

The contracts repo writes deployment outputs to .deployed/<NETWORK>.env, .stellar/contract-ids/<NETWORK>.json, .stellar/wasm-hashes/<NETWORK>.json, and frontend exports such as .deployed/frontend-<NETWORK>.env and .deployed/frontend-<NETWORK>.ts. The indexer must consume these outputs for testnet and local runs.

Implementation checklist

• Add a manifest ingestion script under apps/s03-indexer/scripts/.
• Support a configurable contracts repo path, defaulting to ../contracts or an env var, not a hidden absolute path.
• Read deployment files from /home/sunny/zero/so4-market-project/contracts when using the default local repo layout.
• Generate an indexer-local JSON config such as apps/s03-indexer/config/contracts.testnet.json.
• Include network name and network passphrase in the generated config.
• Include Horizon and Soroban RPC endpoints in the generated config.
• Include core contracts: role_store, data_store, oracle, market_factory, deposit_handler, withdrawal_handler, order_handler, liquidation_handler, adl_handler, fee_handler, referral_storage, reader, and exchange_router.
• Include test token contracts: TUSDC, TWBTC, TETH, TXLM, and faucet.
• Include market tokens and their index/long/short token triplets.
• Validate every contract ID shape before writing config.
• Fail with actionable errors when deployment files are missing or incomplete.
• Allow missing MARKET_TOKEN_* values only before bootstrap, and report them clearly.
• Add package scripts such as sync:contracts:testnet and sync:contracts:local.
• Update project.ts to read contract IDs and endpoints from generated config/env.

Acceptance checklist

• A contributor can deploy/bootstrap contracts, run one sync command, and see indexer config update.
• Local and testnet configs can coexist without overwriting each other.
• The indexer no longer relies on the starter template's generic hardcoded transfer filter.
• Missing or malformed deployment data fails fast with useful error text.

Verification commands

• Run bun run --cwd apps/s03-indexer sync:contracts:testnet.
• Run bun run --cwd apps/s03-indexer build.

[peter-j23]

am a software engineer and an enthusiast in open source projects, I would really like to resolve this issue if assigned. Thank you

[Hassanmovic98]

I will implement a deployment manifest synchronization system that automatically discovers SO4 contracts, tokens, markets, and network configuration from the contracts repository outputs instead of relying on hardcoded identifiers. The solution will generate environment-specific indexer configuration files, validate deployment artifacts, surface actionable errors for missing data, and support both local and testnet environments without configuration conflicts. This will ensure the indexer remains aligned with deployed infrastructure while simplifying setup and reducing maintenance overhead.

[spiffamani]

@spiffamani has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hey,

I'm a full-stack Software Engineer with 3 years of experience and a background in Blockchain development. I'm relatively new to open-source but I pick things up fast and I'm genuinely interested in this issue.
My main stack is React, TypeScript and Next.js on the frontend — I focus on clean component architecture, responsive design and performance. On the backend I work with Node.js, Java and Rust, handling everything from API design to database modeling.
A few things I've built:

https://www.zendvo.com/
https://cleanrest.vercel.app/

I'm comfortable jumping into an existing codebase, following conventions and shipping clean, maintainable code. My GitHub shows the kind of work I do better than I can describe it.
I'd love to take this on — thanks for considering me.

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

[DTriple-p]

@Agbasimere has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi, I'd like to work on this issue.

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

[madisonsc52-del]

@madisonsc52-del has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi maintainer i can work on this, I'll make sure to work on the issue asap

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

[intelliDean]

@intelliDean has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I'd like to work on this issue

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

[0xMegie]

@0xMegie has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi, I'd like to take this on. The aim is for the indexer to discover contracts, tokens, and markets from the deployment outputs instead of hardcoded IDs. I'll add a manifest ingestion script under apps/s03-indexer/scripts/ that reads the contracts repo's .deployed/.env, .stellar/contract-ids/.json, and wasm-hash outputs, with the repo path configurable (default ../contracts or an env var, no hidden absolute paths), and emits an indexer-local config like config/contracts.testnet.json.
The generated config will carry network name + passphrase, Horizon/Soroban endpoints, all core contracts (role_store through exchange_router), the test tokens (TUSDC/TWBTC/TETH/TXLM + faucet), and the market token index/long/short triplets. I'll validate every contract ID shape before writing, fail fast with actionable errors on missing/incomplete files, and treat absent MARKET_TOKEN_ as allowed-only-pre-bootstrap with a clear report. Then sync:contracts:testnet/sync:contracts:local scripts that keep the two configs from overwriting each other, and update project.ts to read IDs/endpoints from the generated config so the starter's generic transfer filter is gone. I'll verify with the sync + build commands on a fresh checkout. I'll wait on Issue #3 first. Could you assign it to me?

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

[grantfox-oss]

🦊 GrantFox — @0xMegie has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #181)
2. Your PR will be reviewed by the SO4-Markets maintainers

Good luck! Track your progress on GrantFox.

[drips-wave]

Congratulations, @0xMegie! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @0xMegie: 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 awarded 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 🌊