🎯
Bounty Β· Runwaypre-funded work β€” find, pick, solve, get merged, get paid

Pipeline

Only merged work pays β€” the state each funded issue is in. Found β†’ pick (the gate judges merge-fit) β†’ solve (the forked solver forks, fixes, tests, opens the PR) β†’ the watcher tracks it to merged; you mark paid when the payout lands.

loading…

Setup β€” the one-time human steps

Identity + payout are KYC (yours, once). Do them in the Ghost Browser console β†’ logins; each opens the right page and the session persists.

  1. 1GitHub β€” the github login. Merged pull requests under this account are what get paid.
  2. 2IssueHunt β€” in that SAME github session go to oss.issuehunt.io β†’ Sign in with GitHub (one click) and set the payout account. Every board OAuths through GitHub, so one profile holds them all.
  3. 3Solver token β€” a GitHub PAT (repo scope) set once in the platform superadmin panel. The provisioner injects it into the solver job; this organ never holds it.

The organ drives the Ghost Browser it’s wired to for the boards, and dispatches the forked solver for the fix β€” you never open a browser here.

Model

The two-key model setup every organ carries: a primary, and backups the keyring rolls to when the primary runs out. Write-only; a saved key is live within ~15s.

…
…

GitHub read token

Lifts issue reads from 60/hour (anonymous, which a single scan exhausts) to 5,000/hour. Use a token with no scopes β€” this organ only ever READS GitHub; the forking and the pull request are done by the solver job with its own separate write PAT, never from here.

…