Solana mainnet slot … SOL …
Put a price on a bug. An agent ships the fix.
Pick an open issue on GitHub, say what a fix is worth in USDC or SOL, and sign that promise with your wallet. You get one card to paste into your coding agent, and a way to check the payment on chain afterwards.
Paste this into your coding agent
Read /pickup.md and follow it.
Then hand it a bounty link from the workbench. Works with any agent that can read a web page.
Example ticket, not a real bounty
50 USDC
≈ … SOL at the live price
How it works in 3 steps
- 1
Find a bug worth fixing
Type a repo name. We list its open issues marked bug, good first issue or help wanted, straight from GitHub.
- 2
Put a price on it and sign
Set an amount. Your signs a short text that says what you will pay and for what. Nothing leaves your wallet.
- 3
Hand the card to an agent
Paste the instruction card into your coding agent, or share the link. When the fix is merged you pay, and anyone can check it.
How it works
From a broken line to a paid fix.
-
01
Scout
Paste
owner/repo. The page asks GitHub for open issues and keeps the ones a newcomer or an agent could really close.your-org/your-repo- #128Crash when the config file is emptybug
- #131Wrong total when two fees share a slothelp wanted
- #140Docs example fails on a fresh installgood first issue
- #152Retry loop never backs offbug
-
02
Price
Choose USDC or SOL. The dollar value follows the live market price, so you always see what the promise is worth today.
50USDC
≈ … SOL right now, read from Jupiter
-
03
Sign
The bounty becomes a few plain lines of text. Its fingerprint is the id. Your wallet signs the text, so nobody can change the amount later.
PATCHPURSE BOUNTY v1 repo: your-org/your-repo issue: #131 amount: 50 USDC terms: first merged pull request that closes it
id pp-········
signed promise -
04
Paid
After the merge you pay wallet to wallet. The payout check reads the funder's recent transfers on Solana and looks for the matching payment.
- scanfunder's last 25 transactionsread-only
- match50 USDC to the recipientpaid
Repo scout
Boards
Open-source projects with fixable issues. Pick a card or type any public repo. Results come live from the GitHub API and are cached in your browser for six hours.
Working tools
Workbench
Three tools, all running in this page against live data. A made here is a signed promise, not an . No money is locked or moved by this site.
0 USDC
Fill the form and press Build bounty.
Signing asks your wallet to sign the text below as a message. It is not a transaction and cannot move funds.
The exact text appears here. Its SHA-256 is the bounty id, so the same text always gives the same id.
The instruction card for your agent appears here once the bounty is built.
A short markdown comment you can post on the issue, so contributors see the bounty.
- Text reads as a bountywaiting
- SHA-256 id recomputedwaiting
- Signature matches the funderwaiting
- Worth todaywaiting
0 USDC
Paste a link and press Verify.
Nothing verified yet.
Result
No check run yet
Fill the form, or try the example: it reads the latest outgoing transfer of a busy public exchange wallet and then looks for it.
- Transactions appear here as they are read.
Saved on this device
Your purse
Bounties you built or opened, kept in this browser only. Room for 6.
Token utility
What the coin is for
Small, real perks inside this tool for people who hold the coin. No promises about price, listings or returns. Connect a wallet to check.
- ready
A bigger purse
Holders keep 40 saved bounties instead of 6. The check reads your wallet's token accounts, nothing else.
- ready
Deeper payout scans
The payout check reads the last 60 transactions for holders instead of 25, so older payments are found.
- ready
Holder mark on tickets
Tickets you build carry a small holder mark in your purse and on the page, so your boards are easy to spot.
- planned
Votes on what ships next
Holders sign a message to vote on roadmap items. Counted from wallet balances, no fees.
- planned
Featured boards
Holders nominate repos for the starter boards above. Maintainers can always opt out.
"Ready" means the code is on this page and switches on the moment the coin address is published here. It becomes "live" then.
Tokenomics
One supply, no side doors
The coin is not live yet. This is the planned structure, labelled as planned, and it will be replaced by live on-chain numbers when the address is set.
- Fixed supply
- 1,000,000,000
- Launch
- Fair launch on pump.fun
- Presale
- None
- Team allocation
- 0% unless bought on the curve like anyone else
- Mint and freeze authority
- Revoked
- Liquidity
- Locked or burned at graduation
- Supply
- …
- Price
- …
- Market cap
- …
- Liquidity
- …
- Top 10 holders
- …
- Sources
- DexScreener and Solana RPC, read live
Flowcharts
Where things go
Two drawings: how a bounty travels, and where the data and the money go. Swipe sideways on a small screen.
Roadmap
What is built, what is next
"Done" means it works on this page today. Nothing unbuilt has a date.
Phase 1 done
The working bench
- Repo scout with caching and a clear rate-limit state
- Bounty builder with live USD value, canonical text and SHA-256 id
- Agent instruction card and an issue comment to copy
Phase 2 done
Proof you can check
- Wallet message signature carried inside the share link
- Ed25519 verification in the browser, with tamper detection
- Payout check that reads recent transfers on Solana mainnet
Phase 3 building
Holder perks and co-funding
- Holder perks, coded and waiting for the coin address
- Several funders signing the same bounty id
- Payout check that follows the address named in a pull request
Phase 4 planned
A public board
- An open index of signed bounties anyone can mirror
- A comment helper for maintainers who want bounties shown on issues
- Roadmap votes by signed message
Phase 5 planned
Optional escrow
- An open-source on-chain escrow for people who want funds locked
- Independent review before anyone is asked to use it
- The signed-promise path stays free and stays the default
FAQ
Plain answers
What is this, in one sentence?
A page that turns a GitHub issue into a priced, signed promise to pay for the fix, plus a ready instruction you can paste into a coding agent.
Is it safe?
The site is read-only. It never asks for a transaction and cannot move funds. Connecting a wallet only shares your public address. Signing a bounty signs a short readable text. Still, read what your wallet shows you before approving anything, here or anywhere.
Is the money locked somewhere?
No. A bounty here is a signed promise, not an escrow. The funder still has to pay by hand after the fix lands. The signature proves who promised what, and the payout check shows whether they paid.
What exactly does my signature do?
It proves that the wallet named as funder agreed to the exact bounty text. Change one character and the check fails. It does not approve spending, and it is not sent to any server: it travels inside the link you share.
Where does the data come from?
Issues come from the public GitHub API. Prices come from Jupiter. Balances and transfers come from a read-only Solana RPC. Saved bounties live in your browser's local storage.
GitHub says "rate limit". Now what?
GitHub allows about 60 anonymous requests an hour per network address. Results are cached for six hours, so wait a little or paste an issue link straight into the bounty builder, which needs no GitHub call at all.
Does the site use AI?
No. Everything here is plain rules: label filters, a hash, a signature check and a ledger scan. The coding agent is yours, running wherever you run it.
Does the payout check prove the fix was paid for?
It proves that at least the amount moved to the recipient in a recent transaction the funder took part in. It cannot know why the payment was made, and it only looks at a recent window of transactions.
What does it cost?
Nothing. There are no fees, no accounts and no backend.