On-chain payroll for GitHub issues.
Lock USDC against an open issue. When the pull request lands in main, the smart contract pays the contributor — no invoices, no Stripe, no accounting back-and-forth.
- Escrow
- On-chain
- Network
- Base · 8453
- Asset
- USDC
How it works
From issue to payout in four steps.
One contract, one merge, one transaction. No back-channel invoicing, no off-chain promises.
- 01
Open the issue
Use GitHub the way you always have. File the bug or feature in your repo and describe the desired outcome.
- 02
Lock the bounty
Connect your wallet, attach a USDC amount to the (repo, issue) pair, and set an expiry. Funds sit in escrow.
- 03
Merge the PR
Review and merge the contributor's pull request on GitHub. No extra UI, no extra dashboard.
- 04
Contract pays
GitPay's oracle reads the merge event and releases USDC straight to the PR author's wallet on Base.
Live preview
Realistic bounty cards.
What a fully-stocked board will look like once the contract is live and projects start attaching budgets to their backlog.
#4218 · watchAccount fires twice on reconnect
#14820 · @theme inline doesn't resolve runtime vars
#2103 · Custom chain icon flickers in modal
#8847 · forge verify-contract fails @1M optimizer
#4912 · BigNumberish overflow on 256-bit return
Examples shown for layout reference — pre-launch state. Live bounties appear once BountyVault is deployed and verified.
Why GitPay
Built for teams that want maintainers paid, not chased.
On-chain escrow
USDC sits inside BountyVault.sol on Base. No GitPay-owned wallet, no custodial surface, no rug vector.
GitHub-linked payout
An oracle observes the merge event from GitHub's API and triggers on-chain release. PR author's wallet receives USDC directly.
Built on Base
Settles in seconds, ~$0.0001 per payout. Native USDC liquidity through Circle's official Base deployment.
No invoices, no NET-30
Skip vendor onboarding, contractor forms, and accounting workflows. Every payout has an immutable BaseScan receipt.