Make leader-election lease renewal safe across clock jumps

[Jagadeeshftw]

Area: Indexer / distributed reliability

Problem

src/indexer/leaderElection.ts coordinates ownership and lease renewal; wall-clock jumps can create false ownership or premature expiry.

Design decision required

Choose monotonic time/DB time and define renewal behavior after a clock anomaly.

Deliverable

Simulate forward/backward jumps, delayed renewal, and restart and assert no split-brain write permission.

Acceptance criteria

• The selected behavior is implemented and covered by focused regression tests.
• Failure, boundary, retry, and authorization behavior is explicit where applicable.
• Existing behavior outside this scope remains unchanged.
• CI output and any performance/resource impact are reported in the PR.

Out of scope

• Typo-only, documentation-only, unrelated refactors, and dependency churn.
• Closing, weakening, or skipping tests to make the change pass.

Verification

pnpm vitest run tests/indexer/leaderElection.test.ts

PR requirements

• Keep the PR focused, explain the before/after behavior, and reference this issue.
• Include the requested regression evidence and relevant CI results.
• Open the PR within 48 hours of assignment or leave a scope question on the issue.
• Contributor discussion: https://t.me/+u5qmu35nZ7I0OTU1

[onyekachi66]

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

I would like to work on this issue having worked on similar issues in the past. Please assign

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

[retkatmun]

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

Hi Maintainer,

I’m a smart contract and full-stack developer and would love to contribute to this issue. I’m an experienced contributor with hands-on expertise in Rust, Soroban, Cairo, and TypeScript.

I’m passionate about building secure, scalable blockchain solutions, with a strong emphasis on writing clean and maintainable code. Based on the scope of this issue, I’m confident I can deliver a complete solution within 24 hours of assignment.

I’d greatly appreciate the opportunity to contribute and help move this forward.

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

[Jagadeeshftw]

@onyekachi66, Wishing you a strong start on this task—please take ownership of the full scope.\n\nYou are assigned to #1295 — Make leader-election lease renewal safe across clock jumps. Please read the complete issue description carefully before starting and begin working on it. Address every requirement, acceptance criterion, and expected behavior mentioned in that description in your PR; the PR should cover the full issue scope and be a high-quality, reviewable contribution. Please use the issue as the source of truth while you work and keep the final contribution polished.\n\nPlease raise the PR within 48 hours of this assignment. If no PR is opened within 48 hours, you may be unassigned so the issue can be offered to another contributor.\n\nPlease also join our Telegram group: https://t.me/+u5qmu35nZ7I0OTU1

[drips-wave]

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

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

[martinshub-tech]

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

I'd like to take this issue. I've analyzed the root cause and am confident I can deliver a reliable fix with proper testing

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

[Muyideen-js]

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

Hi, I can fix this

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

[odinakaikpakingsley-alt]

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

hello maintainer, i'd love to work on this issue! please assign me

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

[pharwasz]

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

Hi, I would like to work on this issue

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

[Moh-dakai]

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

please assign

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

[Samaro1]

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

Gm gm boss. I would like to take this one on. I can decide between monotonic time and DB time for leaderElection.ts's lease renewal and define the renewal behavior after a clock anomaly, implement it so ownership and expiry stay consistent under forward/backward wall-clock jumps, and cover it with the simulated forward/backward-jump, delayed-renewal, and restart tests asserting no split-brain write permission, opening the PR within 48 hours of assignment. Please assign it to me.

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

[drips-wave]

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

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