[Backend] backend/src/services/indexerService.ts and soroban-indexer.service.ts have near-identical names but different responsibilities, confusing new contributors

[grantfox-oss]

Join our community: https://t.me/+DOylgFv1jyJlNzM0

Why this matters

backend/src/services/indexerService.ts and backend/src/services/soroban-indexer.service.ts sit side by side with overlapping names (one is camelCase-named, the other kebab-with-suffix), and separately from backend/src/workers/soroban-event-worker.ts which is flagged elsewhere as running a second, racing indexer. Beyond the functional race already tracked, the naming itself makes it hard for a new contributor to know which file to read first when debugging indexing.

Acceptance criteria

• Document (in a code comment or docs/ARCHITECTURE.md) which service is the source of truth and which is legacy/being phased out
• Align file naming convention (both kebab-case with .service.ts, or both camelCase) once the functional consolidation (tracked separately) lands

Files to touch

• backend/src/services/indexerService.ts
• backend/src/services/soroban-indexer.service.ts
• docs/ARCHITECTURE.md

Out of scope

• Fixing the double-indexer race condition itself (tracked separately)
• Renaming worker files

[OpensrcLord]

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

Hello @maintainer, I’d like to work on this issue. I have experience handling similar tasks and can start immediately. And I will deliver at the shortest possible time.

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

[alade-dev]

@alade-dev has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hi, I would love to work on this issue.

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

[drips-wave]

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

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