GrantFox, bounties, and getting paid for open source work

Platforms like GrantFox connect open source contributors with funded issues — bounties on bugs, features, and integrations, often in the Web3 ecosystem. It sounds like free money for work you'd do anyway. The reality has more texture, and knowing it changes how you approach bounties.

What bounties actually test

Scope reading. A bounty post is a requirements document. Half of bounty disputes come from contributors who fixed the bug as they understood it, not as it was specified. Read the acceptance criteria like a contract — because it is one.

Proof of work. Payment follows a merged PR and verified acceptance. That means the full contribution discipline applies: minimal repro, focused diff, tests, clean description. A bounty is just an issue with a deadline and a price.

Payment rails reality. Many Web3 bounties pay in tokens or need wallet setups. Before investing an evening, understand how you'll actually be paid, and what it costs to convert it to money you can use. In Nigeria, that calculation includes rails that don't always exist in the global imagination.

What makes it worth doing

The bounties that pay best aren't the highest-priced ones — they're the ones adjacent to skills you're already building, in projects you'd happily contribute to for free. Then the payment is a bonus on work that was already an investment.