← Blog · published Oct 6, 2026
Coding bounties: what they are, where to find them and how they pay
A coding bounty is money attached to a piece of work — most often an open GitHub issue — that is paid to whoever delivers a solution the maintainer accepts. This guide explains how the system works, where to look and how to avoid wasting hours on bounties that will never pay.
How a coding bounty works
A maintainer, company or sponsor funds an issue through a bounty platform. Contributors signal they are working on it, open a pull request that fixes the issue and reference the bounty. If the maintainer merges the pull request, the platform releases the payment according to its own rules, which can include payout setup and a waiting period.
Where coding bounties are listed
The main platforms are Algora, Opire, IssueHunt, BountyHub and TaskBounty. Each has its own commands and payout flow, so read the platform documentation before you start. Because the listings are spread across platforms, the practical problem is not finding a bounty but deciding which one deserves your time.
How to pick a winnable bounty
Favour issues that are open and unassigned, in a repository that was active recently, with few or no competing pull requests and a clear, small scope. Freshness matters: a bounty posted hours ago has not yet attracted a pile of attempts. Ignore listings where the amount looks too good for a brand-new repository.
Mistakes that cost hours
Starting on an issue that already has a merged fix, ignoring the contributing guide, opening a huge pull request instead of a focused one, and not re-checking that the bounty still exists before you submit. Our checklist for spotting fake or farmed bounties covers the common traps.
Getting paid
Payment depends on the platform and on the maintainer merging your work. Set up your payout details early, keep your pull request easy to review and be patient: the review step is the part you do not control.
A faster way to shop
BountyOS scans the platforms every hour, scores each verified bounty from 0 to 115 (confirmed payout, dollar tier, freshness, competing pull requests, repository health) and alerts you to the fresh ones. The live board shows what is open now; the dashboard unlocks repositories and links.
FAQ
What is a coding bounty? A coding bounty is a sum of money attached to a specific task, usually an open GitHub issue. Whoever delivers a solution that the maintainer accepts gets paid, typically through a bounty platform that holds or releases the funds.
Where are coding bounties listed? Mainly on platforms such as Algora, Opire, IssueHunt, BountyHub and TaskBounty, plus issues where a maintainer or sponsor posts a bounty directly in the repository. A radar that scans them together saves you from checking each one by hand.
Can beginners earn from coding bounties? Yes, but expect competition and unpaid attempts. Smaller, well-scoped issues in active repositories are the realistic starting point; large bounties usually attract experienced contributors.
Are all coding bounties legitimate? No. Some are self-funded by the repository owner, some sit on abandoned or brand-new throwaway repositories, and some are already solved. Check the repository and the issue history before you invest time.
See also: How to claim an Algora bounty · How to spot fake bounties · Live bounty board