GitHub Bounties

V2-4 parallel hunt

GitHub BountiesGitHub Bounties

USDC bounties on GitHub issues. Winner is the author of the merged pull request that closes funded issue #N. Parallel hunt; merge is truth.

Browse the boardPost a bountySign in
Fee
2%
fee_bps = 200
Hunt
Parallel
optional Working on this, not exclusive
Rail
USDC
chain base · rail Base (CDP)

Live platform stats

From this environment via getPlatformStats (same as GET /api/stats).

GET /api/stats·schema v2

Bounties
5
Every bounty_status. Sum of open + completed + closed + in-flight.
Open
1
pending_fund + funded + claim_locked (product open / fundable).
Completed
4
settled + settled_partial — Completed (paid) / Winner paid — pool pending.
Closed
0
refunded + cancelled + expired + void (terminal unpaid).
USDC volume
12.33 USDC
Face that reached a funded or settled money event. Excludes fees.
Developers
5
Distinct hunters. Poster-only users are excluded.
Repos with bounties
3
Distinct repos with ≥1 bounty row (any status). Not bare GitHub App installs.

Use it from your AI agent

The public API and the MCP server let Cursor, Claude, and other agents read the board and act with your API key. Same rules as the website.

MCP

vs Lightning Bounties

This is not Lightning Bounties, LB1, or “Lightning Bounties 2”. About the team

  • Fair hunter economics

    V2 pool: 2% fee, then 85% to the winning merge author and 15% of post-fee split equally among up to 10 eligible hunters. Empty pool still pays the winner 98% of face.

  • USDC on Base, not Lightning

    Settlement is USDC via CDP escrow + x402 — not Lightning Network invoices or LN balances.

  • 2% platform fee

    fee_bps = 200, taken at settlement only. Face locks in gb-escrow; 2% goes to gb-fee. No hidden skim.

How a bounty moves

Six steps already in the product. Scroll moves the picture. It does not change the fee, the escrow, or who can claim.

  1. 01

    Paste a GitHub issue

    The issue stays the work

    Post a bounty by pasting a GitHub issue URL. The public board lists it, and the bounty page keeps the full issue. This does not open a second tracker.

    Post a bounty

  2. 02

    Secure USDC escrow

    Face locks in gb-escrow

    Fund locks the face amount of USDC in gb-escrow via x402 exact. The 2% fee is taken at settlement, not at fund. Cancel or expiry refunds the full face. Hosted checkout is disabled.

  3. 03

    AI bounty intelligence

    Estimates only

    A server-side card summarizes the repo (about and language stack) and estimates issue complexity as S, M, or L. Those are cached AI estimates — not a price and not a payout. If the model key is missing, the bounty page still works.

  4. 04

    Fair 85/15 hunter split

    Post-fee winner / pool

    After the 2% fee, 85% of post-fee goes to the winning merge author and 15% of post-fee is split equally among up to 10 eligible hunters. An empty pool pays the winner 100% of post-fee (98% of face). A participation pool for eligible hunters — not a public fundraise.

  5. 05

    Merge / Claim

    Merge is truth

    The winner is the author of the merged pull request that closes funded issue #N. They claim their winner share to a bring-your-own Base address. Each pool member claims their own frozen share. Optional Working on this does not pay anyone, and the exclusive claim-lock is retired.

  6. 06

    Global Base settlement

    USDC on Base

    Settlement is USDC on Base, to any bring-your-own Base address. The chain is Base — not Lightning, and not a second network.

This is not Lightning Bounties, LB1, or “Lightning Bounties 2”. Sign in with Google. About · MCP · Roadmap · Board · Post a bounty · Sign in · Settings. Exclusive claim-lock is retired; merge is still truth. Eligible winners claim their share to a BYO Base address. Pool members are paid to Settings wallets when settle runs. Escrow holds face in gb-escrow; 2% to gb-fee at settlement. Hosted checkout is disabled.