← Blog · published Oct 3, 2026
How to claim an Algora bounty, step by step
Algora is one of the main platforms that fund GitHub issues. This guide covers the practical flow from finding an issue to submitting a pull request. Command syntax can change, so always confirm it in the platform's own documentation before you rely on it.
1. Check that the bounty is real and still open
Before writing code, open the issue and confirm four things: the issue is open, the bounty is still listed on the platform, nobody has already been assigned, and there is no merged pull request that already solves it. Many wasted hours come from skipping this step. A merged pull request that references an open issue often means the work is already done and the maintainer simply forgot to close it.
2. Look at the competition
Open the issue's linked pull requests and cross-references. Several open pull requests on the same issue lower your odds, and a swarm of bot-generated attempts is a warning sign. Fresh bounties with no competing pull requests are the best value, which is exactly why a radar that tracks freshness and competitors saves time.
3. Signal that you are working on it
On Algora you typically comment /attempt #ISSUE_NUMBER on the issue so the maintainer and other contributors can see you are on it. It does not reserve the bounty, but it is expected etiquette and it shows up in the platform.
4. Read the contributing rules, then build and test
Follow the repository's contributing guide, code style and test requirements. Small, focused pull requests are merged faster than large ones. If the project has an AI-generated code policy, respect it: some maintainers close such pull requests on sight.
5. Open the pull request and claim the bounty
In the pull request description, reference the issue and include the claim command the platform documents (on Algora, /claim #ISSUE_NUMBER). Explain what you changed and how you tested it, so review is easy.
6. After the merge
Once the maintainer merges your pull request, the platform handles the payout according to its own process, which can involve payout setup on your side and a waiting period. Complete your payout details on the platform in advance so you are not blocked later.
Where a radar helps
The slow part is not the claim, it is deciding which issue deserves your time. BountyOS scores each verified bounty by confirmed payout, dollar tier, freshness, competing pull requests and repository health, and flags honeypots and farmed listings. The live bounty board shows what is open right now; the dashboard unlocks the repositories.
FAQ
Do I need permission before I start working on a bounty issue? Usually you do not need approval, but you should read the issue and the repository contributing guide first. Some maintainers ask contributors to be assigned before opening a pull request, and a PR that ignores the project rules is likely to be closed.
What happens if two people submit a fix? Platforms generally pay the pull request the maintainer chooses to merge, so being first is not a guarantee. A clean, well-tested pull request that follows the repo conventions has the best chance.
Is the amount shown on the issue guaranteed? The bounty is funded by the maintainer or sponsor through the platform, but you should confirm the bounty is real and still open before investing time. Check the platform page and read the issue comments for changes.
See also: GitHub bounty hunting guide · Open source bounties guide · Live bounty board