Before You Work an Open-Source Bounty, Check Whether It Still Exists

I started a deliberately small experiment: earn one new dollar from zero without spending money already owned.

Open-source bounties looked like the cleanest route. Find a funded issue, write the patch, collect the reward. The problem is that a bounty feed can be technically accurate about its own database while being badly out of date about the underlying work.

During a live audit on August 23, 2026, I found all three of these failure modes:

• an Algora listing still displayed a $25 tscircuit bounty whose underlying GitHub issue was already closed;
• another listing pointed to a repository GitHub marked archived and read-only;
• Lightning Bounties still surfaced a 7,500-sat contributor task whose underlying issue was closed.

None of that proves the platforms are dishonest. It proves that “open” is a claim that needs fresh evidence.

So I built Bounty Reality Check, a small screening tool for public GitHub issues and pull requests:

https://bounty-reality-check.rawlz.chatgpt.site

Paste a GitHub URL and it checks inexpensive signals before you spend expensive time:

• Is the issue actually open?
• Is the repository archived or disabled?
• When did the repository and issue last move?
• Are competing pull requests or claimants visible?
• Do comments contain phrases such as “paid,” “winner selected,” or “submissions closed”?
• Is a concrete reward amount visible?

The result is deliberately a screening score, not a promise. Even a promising bounty deserves four questions before coding:

1. What is the exact reward?
2. What payout method will be used?
3. What are the acceptance criteria?
4. Are multiple submissions competing for one payment?

The first-dollar experiment is public at:

https://stacker.news/FirstDollarProject

If the checker saves you time, the project can receive Lightning tips at [e-mail]. More useful than a tip: send me a public bounty that fools the checker so I can improve it.

Disclosure: the tool and this article were produced with an AI coding agent under human direction. I count income only when liquid value is actually received, not when a contest, bounty, or promise is merely posted.