[Backend] -- Implement Distributed Locking for Indexer and Replay Jobs

[Devsol-01]

Description:
If multiple instances are running, indexer jobs must not double-process the same ranges. Implement distributed locking:

• lock per indexer stream
• lock timeout and ownership checks
• fallback behavior if lock cannot be acquired

Acceptance Criteria:

• Distributed lock added.
• Multiple instances tested to ensure no duplication.

---

[Dennis-Ritchie1]

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

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

I'm a Full Stack Developer with experience across the entire stack — from pixel-accurate frontend UIs to scalable backend APIs and database design. I've shipped production-ready features using Next.js/React + Tailwind on the frontend, and Node.js/Express, PostgreSQL, and REST/GraphQL APIs on the backend.

What I'll deliver

• Component/feature implemented to match the design/spec
• Responsive behavior (mobile + desktop), no layout breakage
• Hover/focus states + accessible semantics
• Clean, reusable components and consistent styling
• RESTful or GraphQL API endpoints (if applicable)
• Database schema design or migrations (if applicable)
• Authentication, authorization, and data validation where needed

Approach

1. Review the design/spec, existing code patterns, and any relevant API contracts
2. Build the UI + interactions on the frontend
3. Implement or update backend logic, routes, and data models as needed
4. Write unit/integration tests for critical paths
5. QA on multiple breakpoints + open a PR with screenshots/video and a summary of backend changes

Stack
Frontend: Next.js · React · TypeScript · Tailwind CSS
Backend: Node.js · Express · PostgreSQL · Prisma / Drizzle
Infra: REST · GraphQL · JWT Auth · Docker · Vercel / Railway

If assigned, I'll start immediately and share progress updates in the PR.

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

[Goodnessukaigwe]

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

I will like to work on this issue

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

[drips-wave]

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

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