Skip to content

MRWK bounty: active attempt reservations for bounty work #321

@ramimbo

Description

@ramimbo

MRWK Bounty

Reward: 250 MRWK per accepted award
Max awards: 2

Work Needed

Reduce duplicate agent work by adding an advisory active-attempt reservation path for bounty work. The goal is to make it visible when someone is already working on a bounty before more agents open overlapping PRs.

Useful accepted work can include:

  • Add a small attempt/claim model for bounty work with submitter identity, bounty id, source URL or branch/PR URL when available, status, and expiration time.
  • Add API, MCP, or public/admin surfaces that let agents register, inspect, release, or expire active attempts.
  • Enforce one active attempt per submitter per bounty while allowing maintainers to see or clear stale attempts.
  • Warn when a bounty has multiple active attempts, is closed, is paid/exhausted, or has no award slots remaining.
  • Document how agents should use attempts before opening PRs.

Acceptance Criteria

  • Open a focused PR that links this issue with Bounty #<issue number> or Refs #<issue number>.
  • Attempt reservations must be advisory. They must not create payments, claim acceptance, mutate ledger balances, or prevent maintainers from accepting useful work.
  • Expiration behavior must be deterministic and tested so abandoned attempts do not block future work.
  • Include tests for duplicate active attempt rejection, expiration, release or status update behavior, closed/exhausted bounty rejection or warning, and read-only visibility.
  • Preserve existing bounty, ledger, webhook, wallet, and payout behavior.
  • Existing checks pass.
  • One award per distinct useful accepted attempt-reservation improvement. Generic docs-only changes, broad dashboards, or unrelated anti-spam ideas do not qualify.
  • Do not post private keys, seed material, secrets, private vulnerability details, deployment credentials, or price claims.

How To Submit

Open a focused PR with the required evidence. A maintainer must apply mrwk:accepted or record an admin payout before payment.

Metadata

Metadata

Assignees

No one assigned

    Labels

    apiPublic API behaviorenhancementNew feature or requesthelp wantedExtra attention is neededmrwk:bountyMRWK bounty is postedmrwk:paidLedger payment recordedtestsTest coverage

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions