Indexer Resilience & Reorg Recovery

[dDevAhmed]

• 📚 Overview: Refactor the IndexerService to handle chain reorganizations and ensure data idempotency.
• 🎯 Objectives:
  • Implement block sequential queue
  • Transactional block persistence
  • Intelligent RPC backoff
• 🧠 Problem Context: The current indexer can double-process events or fail to roll back state on orphaned blocks.
• 🧩 Technical Scope: IndexerService.ts, EventProcessor.ts, Prisma schema.
• ✅ Acceptance Criteria:
  • Successful recovery after 10-block reorg in local test
  • Idempotent processing confirmed by duplicate logs
  • Backoff logic handles 429 errors
• 🔐 Security / Integrity Considerations: Incorrect indexing leads to stale balances and broken protocol invariants.
• ⏳ Complexity & Effort: High
• 🔗 References: Internal Ref #BE-MATURE-001
• 🏷️ Labels: backend, realtime, database, stellar-wave, complexity-high

---

[mikkyvans0-source]

@mikkyvans0-source has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

hello am a full-stack blockchain dev will ng to work on this project

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

[drips-wave]

Congratulations, @mikkyvans0-source! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

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