Skip to content

Inconclusive proofs with zero available validators are stuck in VERIFYING forever #81

Description

@cybermax4200

Why this matters now: Capacity gap — if no community validators are active, legitimate proofs never resolve and never get paid.

Problem / What: verificationWorker.ts:154-179 calls assignValidators; if no validators exist (assignValidators returns 0, validatorService.ts:41), it logs "needs manual review" but the proof stays VERIFYING with no admin auto-escalation and no queue of such proofs. There is no endpoint or sweeper that surfaces "VERIFYING but unassigned/expired-assignment" proofs for human action.

Key Challenges: Defining an escalation path (admin review queue filter, or auto-reject-after-TTL), and ensuring it doesn't collide with the finalization race fix in #1.

Acceptance Criteria:

  • A proof that cannot be assigned validators is moved to an explicitly reviewable/escalated state within a bounded time.
  • An admin can list and act on these proofs (or they auto-resolve) — test.

Relevant files/functions: src/workers/verificationWorker.ts:154-179, src/services/validatorService.ts:20-52, src/controllers/proofController.ts:listPendingProofs.

Out of scope: Auto-recruiting validators.

Labels: advanced, reliability, bug

Activity

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

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions