Beta The Base Sepolia testnet is live — try it with test USDC.

Bounties for GitHub issues
that pay themselves.

Fund an issue in USDC. When the PR merges, the contributor gets paid automatically — no claim, no invoice, no middleman.

How it works
Open source & self-hostable — run it fee-free
Non-custodial escrow
Auto-payout on merge
Refunded if unsolved
How it works

Three steps. The merge does the rest.

01

Post a bounty

Pick one of your open issues and fund it with USDC. The funds lock in an open-source escrow contract on Base — you only pay gas.

02

Solve & merge

Contributors open a PR that closes the issue. Merge it into your target branch — the merge is the authorization, nothing else to click.

03

Get paid

The bounty disburses automatically to the contributor's linked wallet, minus a small fee. Unmatched bounties are refunded to the funder after expiry.

Pricing

Fair fees, or none at all.

Use GitReward Cloud for a flat cut on payout, or self-host the open-source stack and pay nothing.

Cloud Recommended
3% per paid bounty

We run the neutral oracle and infrastructure. You just fund an issue and merge the PR.

  • Charged only on a successful payout
  • Hard-capped at 10% in the contract — we can't charge more
  • Neutral oracle signs every payout
  • No fee on refunds, ever
Self-hosted Open source
0% set your own fee

Run GitReward for your own organization. Call setFeeRate(0) and pay nothing.

  • MIT-licensed escrow contracts on Base
  • AGPL-3.0 platform — deploy the whole stack
  • You run your own oracle and treasury
  • No protocol cut — keep 100%
View on GitHub
Trust & custody

How your money is handled

Plain English — non-custodial, one neutral oracle, you only pay gas to fund.

Where does the money sit?

In an open-source escrow contract on Base — not in our bank account. We can't spend it and we can't stop a refund. You only pay gas to fund it.

What do I actually trust you with?

One thing: when a bounty PR is merged, we (a single neutral oracle) sign a message that says “pay this contributor.” The contract checks our signature and pays out. That signature is the only power we hold — and it can only pay the address the contributor themselves linked. It cannot redirect funds anywhere else.

What if GitReward disappears?

Every unmatched bounty is refundable to the funder after its expiry — no fee, and nothing for us to approve. That refund path is permissionless and outside our control, so no one can strand your money, even if we vanish.

How does a contributor get paid?

They link a payout wallet once, then solve issues normally. On merge, the bounty disburses to that wallet automatically — no claim step, no invoice. If they haven't linked a wallet by merge time, the bounty is refunded to the maintainer after expiry.

What's the fee?

3% on GitReward Cloud, charged only when a bounty pays out — well under the 20%+ that's normal elsewhere. It's hard-capped in the contract at 10%, so we literally cannot charge more, by design. Self-hosters set the fee to zero and run fee-free.

Is it really “trustless”?

No — and we won't claim that. It's non-custodial with one neutral oracle. That's an honest, smaller claim than “trustless,” and it's the one we can actually stand behind.

Get started

Fund your first issue
in minutes.

Sign in with GitHub, pick an open issue, lock USDC. The merge pays it out.