Skip to content

PREWAVE-BE-069 — Add Leader Election and Fencing for Singleton Background Jobs #666

Closed

Description

@dDevAhmed

Problem context

Source audit identified this distinct API production-readiness boundary.

Technical scope

Use DB/Redis leases with fencing tokens for migrations, rebuilds, retention, schedulers, and reconciliation jobs.

Required tests

Two workers, lease expiry, clock skew, partition, slow holder, restart, and stale token tests.

Acceptance criteria

  • At most one current leader mutates a singleton job.
  • Stale leaders are fenced.
  • Lease loss stops work safely.
  • Takeover is bounded/audited.

Constraints

Canonical finalized contract events remain authoritative. Bind chain data to chain/release/artifact provenance; fail closed on stale, ambiguous, unauthorized, or incomplete state. Do not weaken CI or expose secrets/protected data.

Dependencies

Non-goals

Unrelated work, mainnet deployment, or applying Stellar Wave before maintainer activation.

Complexity and points

  • High — 200 points

Candidate only; activation remains maintainer-controlled.

Activity

  1. Olabsy19 commented on Oct 15, 2026

    @Olabsy19
    Contributor

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

    Hello maintainer! If you entrust me with the responsibility of solving this issue, I guarantee you of the amazing solution I will provide and you won't be disappointed.
    Thanks!

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

  2. mubking commented on Oct 15, 2026

    @mubking

    Hi, I'm Mubarak — a Full-Stack & Blockchain Developer with 3+ years of experience. I've reviewed this issue and I'm confident I can handle it. I'll submit a clean PR within 2–3 days. Please assign it to me!

  3. drips-wave commented on Oct 16, 2026

    @drips-wave

    Congratulations, @Olabsy19! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.

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

  4. drips-wave commented on Oct 20, 2026

    @drips-wave

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

    😎 @Olabsy19: You earned 200 Points for completing this issue! Once the Wave's rewards are finalized, 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions