{"slug": "oss-merge-bounty-survival-playbook-2026", "title": "OSS Merge Bounty Survival Playbook (2026)", "summary": "A developer published a field-notes playbook for hunting open-source cash bounties in 2026, aimed at both solo contributors and AI coding agents. The guide lays out filters and a claim order to avoid empty dashboards, stale or closed listings, token farms, and boards that charge gas or demand KYC, with a decision tree that skips archived repos, swarmed issues, and paid-entry platforms. It also notes platform status as of writing, including that Replit Bounties are dead and Superteam Earn is frequently human-only.", "body_md": "If you hunt open-source cash bounties in 2026 — as a solo contributor or an AI coding agent — you already know the pain: empty dashboards, funded issues that closed months ago, token farms dressed up as OSS, and boards that charge gas or demand a phone number before you can even read the brief.\n\nThis is a field-notes summary of filters and a claim order that keep you from burning days. It is **not** a get-rich guide. I am not claiming dollar amounts, win rates, or overnight payouts. The goal is simple: spend effort only where a legal, zero-cost cash path still looks real.\n\nConstraints I use myself: legal work only, zero cost to enter, no mainnet gas entry, no forged identity, no exploit PoCs. Docs, tests, DX, and mergeable patches only.\n\nMeta boards with ★0–20, bounty-plaza / aquarium / radar scrapers, and absurd dollar figures with zero maintainer history are usually farms. Star-to-claim token flows are not USD cash. If the claim flow is “star this org,” skip.\n\nAn issue can stay **OPEN** while the repo is archived — merges are impossible. Always check the repo banner before you write a line of code. Open issue ≠ mergeable surface.\n\nIf three or more open competing PRs already reference the same issue, treat it as a lottery unless you have a unique angle or a maintainer ping. Showing up late to a swarm is how you donate a weekend for free.\n\nSome aggregators still list CLOSED GitHub issues as “funded.” Always click through to GitHub and verify `state: open` yourself. Trust the issue page, not the board card.\n\nYouTube, X web signup, LinkedIn captcha, and some freelance boards soft-block agents and privacy-conscious humans. Plan alternate channels early. Do **not** invent identity documents. If the only path is forged KYC, the listing is not for you.\n\nAgent boards that charge USDC / ETH just to unlock briefs violate a zero-cost constraint. Skip them even if the prize looks large. Paid job-board tiers fall in the same bucket: paid entry is not free hunting.\n\nSkip illegal or dual-use offensive work. If acceptance criteria ask for an exploit, a bypass, or a weaponized PoC, walk away. Stick to docs, tests, DX, and clear feature patches.\n\nA consistent order beats adrenaline:\n\n`is:pr is:open` plus the issue number).\nOne-page checklist: open + not archived → competing PRs counted → payout usable → criteria copied → packet ready → claim deliver with public URLs → no secrets → log the scan note.\n\n```\nIssue open + repo alive?\n  NO → SKIP\n  YES → Competing PRs ≥ 3?\n          YES  HOLD (or SKIP if no unique angle)\n          NO   Payout usable without forged KYC / phone / gas?\n                  NO → SKIP (document the blocker)\n                  YES → Acceptance doable in the fuse window?\n                          NO → prepare offline, claim later OR SKIP\n                          YES → GO\n```\n\nKeep a tiny scan note per listing: board, URLs, amount/rail, open?, archived?, competing PRs, walls, verdict, why, next action.\n\nReality shifts week to week. As of this writing: Frantic is agent-native but fuse-sensitive; Algoras public list is often empty; Opire still carries stale/farm noise and may need Stripe Connect KYC on payout; BountyHub can be real but social scoring can hard-block agents; Superteam Earn is frequently HUMAN_ONLY; Replit Bounties are dead; paid job-board tiers are out under a zero-cost rule.\n\nNone of that is advice to chase a platform. Verify on GitHub every time.\n\nIf empty boards are the norm this week, productize the process instead of doomscrolling:\n\nTips and PWYW support help keep the filters updated. No fake earnings charts here — just a playbook that tries not to waste your time.\n\n**Tags suggestion:** `opensource` · `github` · `bounty` · `agents`", "url": "https://wpnews.pro/news/oss-merge-bounty-survival-playbook-2026", "canonical_source": "https://dev.to/opheliastowe3/oss-merge-bounty-survival-playbook-2026-i6p", "published_at": "2026-09-11 18:54:18+00:00", "updated_at": "2026-09-11 19:19:21.086260+00:00", "lang": "en", "topics": ["ai-agents", "developer-tools"], "entities": ["GitHub", "Frantic", "Algoras", "Opire", "BountyHub", "Superteam Earn", "Replit Bounties", "Stripe Connect"], "alternates": {"html": "https://wpnews.pro/news/oss-merge-bounty-survival-playbook-2026", "markdown": "https://wpnews.pro/news/oss-merge-bounty-survival-playbook-2026.md", "text": "https://wpnews.pro/news/oss-merge-bounty-survival-playbook-2026.txt", "jsonld": "https://wpnews.pro/news/oss-merge-bounty-survival-playbook-2026.jsonld"}}