Launch ingesters per network in the bootstrap

[Miracle656]

Background

src/index.ts starts exactly one instance of each of the five ingesters (SDEX, AMM, Soroswap, Snapshot, Aquarius). Depends on L047–L050. To index both networks, each ingester must be launched per enabled network.

What to build

Iterate enabled networks and start each ingester with its network context.

Key files

• src/index.ts (ingester startup, ~173-177)

Suggested execution

git checkout -b feat/multi-network-ingesters

1. Read enabled networks (e.g. NETWORKS=testnet,mainnet)
2. For each network, start each ingester with getNetworkConfig(network)
3. Ensure restartIngester tracks instances per (ingester, network)

Acceptance criteria

• Each ingester runs once per enabled network
• Restart logic isolates per-network instances
• Single-network mode still starts five loops, not ten

Drips Wave · Complexity: Intermediate · 150 points

---

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

[bridgetthnkechi87-cloud]

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

Hello maintainer, I would love to work on this issue

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

[escaprt]

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

I’m interested in working on Issue #117 because supporting multiple Stellar networks requires the indexing system to treat each network as its own ingestion process. Starting only one instance of each ingester means one network can be indexed while the other is left out.

I will first review the current bootstrap logic in src/index.ts and the existing network configuration to understand how ingesters are created and restarted. I will then update the startup flow to read the enabled networks and launch each ingester with the appropriate getNetworkConfig(network) context.

The restart logic will also be updated so every ingester instance is identified by both its ingester type and network. This will prevent a failure or restart on testnet from affecting the corresponding mainnet process.

I will ensure single-network deployments remain backward compatible. When only one network is enabled, each of the five ingesters should still run exactly once rather than creating duplicate loops.

After the changes, I will test multi-network and single-network configurations and verify that SDEX, AMM, Soroswap, Snapshot, and Aquarius each start correctly for every enabled network. I will also test the restart behavior to confirm that instances remain isolated.

The goal is to provide a clean multi-network bootstrap while keeping the existing single-network deployment behavior unchanged.

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

[kaylachi]

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

I can take this on. I have a clear plan to launch and manage ingester loops per enabled network in Miracle656/Lens.

Implementation Plan

Multi-Network Ingester Management (src/index.ts):

• Update the startup logic in src/index.ts to iterate through all enabled networks defined in the environment configuration (e.g., NETWORKS=testnet,mainnet).
• Instantiate and launch each active ingester (SDEX, AMM, Soroswap, Snapshot, Aquarius) with its corresponding network context retrieved via getNetworkConfig(network).
• Ensure single-network mode defaults to launching only five loops for the configured network without duplicate initializations.

Restart Logic Isolation:

• Update restartIngester to index and track instances using a combined (ingester, network) key.
• Ensure failure recovery or manual restarts on one network instance operate in isolation without affecting active ingester loops running on other networks.

Verification & Testing:

• Test single-network execution to verify exactly five ingesters launch cleanly.
• Test dual-network execution (NETWORKS=testnet,mainnet) to confirm 10 isolated ingester loops start, process events, and restart independently upon failure.

I will submit a pull request with the multi-network ingester bootstrap and instance tracking updates once assigned.

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

[Olorunfemi20]

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

Hi! I'd like to take on this issue. I'll update the bootstrap to iterate over the configured enabled networks and launch each ingester with its corresponding network context, while tracking restart state independently per ingester/network pair. I'll also verify single-network mode remains unchanged and add tests to confirm the correct number of instances and isolated restart behavior across networks.

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

[drips-wave]

Congratulations, @Olorunfemi20! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @Olorunfemi20: 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 🌊