[Backend] indexer-state.ts singleton row has no migration guard against concurrent first-insert race

[grantfox-oss]

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

Why this matters

backend/src/lib/indexer-state.ts creates the singleton indexer_state row on first access; if the worker and an admin reset endpoint both start cold at the same time, two concurrent inserts can race on the same conceptual singleton before the unique constraint kicks in, and the failure path is not handled gracefully.

Acceptance criteria

• Wrap the first-insert logic in a catch that treats a unique-constraint violation as success and re-reads the row
• Add a test simulating a duplicate insert and asserting it does not throw

Files to touch

• backend/src/lib/indexer-state.ts

Out of scope

Does not change the indexer_state schema.

[dahmeezy]

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

I would love to work on this issue, please assign it to me

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

[Smartdevs17]

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

can I work on this?

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

[Vivian-04]

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

Hiiiiiiiiii, I would love to work on thissssssss for youuu! I have experience building resilient backend services and handling database concurrency edge cases. I can update the singleton initialization logic in indexer-state.ts to gracefully handle concurrent first-insert races by treating unique-constraint violations as a successful initialization and re-reading the existing row. I'll also add a test that simulates the duplicate insert scenario to ensure the race condition is handled without errors while keeping the schema unchanged. ETA: a few hours.

Thank you for the consideration.....Thank youuuuuuu!!

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

[drips-wave]

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

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

[drips-wave]

This issue has been completed by @Smartdevs17 as part of the Stellar Wave Program's 7th Wave 🥳

😎 @Smartdevs17: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.