You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Inconclusive proofs with zero available validators are stuck in VERIFYING forever #81
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.
Hi, I’d like to work on this issue. From reviewing the current flow, assignValidators() returning 0 leaves the proof in VERIFYING without an explicit escalation indicator.
Before I begin, would you prefer:
immediate escalation to the existing admin-review queue when no validators are available, or
automatic resolution after a configurable TTL?
I’ll include regression tests and ensure the escalation is idempotent under worker retries. Please assign this issue to me if it’s available.
Activity
kawmy commentedon Aug 22, 2026
Hi, I’d like to work on this issue. From reviewing the current flow, assignValidators() returning 0 leaves the proof in VERIFYING without an explicit escalation indicator.
Before I begin, would you prefer:
I’ll include regression tests and ensure the escalation is idempotent under worker retries. Please assign this issue to me if it’s available.
grantfox-oss commentedon Aug 23, 2026
🦊 GrantFox — @kawmy has been assigned to this issue as part of the Third Campaign campaign!
Next steps:
Closes #81)Good luck! Track your progress on GrantFox.
grantfox-oss commentedon Aug 24, 2026
🎉 This issue has been marked as completed on GrantFox as part of the Third Campaign campaign!
@kawmy's PR #97 was approved and merged by @cybermax4200.
🏆 @kawmy: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (83 total points). Track your full progress on GrantFox.
👏 Great work, @kawmy! Keep contributing to ecotask-network.