Docs
Send a repository money it never asked for.
Somebody writes the library. Somebody else launches a token. CO-FEE wires the second one's trading fees to the first one's GitHub repository — no email, no signup, no meeting. The money starts collecting whether or not anyone has noticed.
01 · The whole thing
Four steps, and the developer does nothing for the first three.
That is the point. Paying open source normally needs the maintainer to show up, sign something and claim. Here the money is already waiting when they arrive.
- Someone launches a tokenIn the same transaction, its trading fees are pointed at one GitHub repository. Not afterwards — inside the launch itself.
- The repository gets a vaultAn address derived from GitHub's numeric repo id. It exists before anyone deploys it, so a launch can aim at it straight away. no signup
- Fees pile up on their ownEvery trade adds to them. A pass runs every five minutes, collects what pons owes, and books the bigger share to the repository.
- A maintainer takes the moneyOne small file on the default branch proves who they are. The balance waits as long as it needs to — there is no deadline. FUNDING.json
02 · If you want to launch
Four things to do, about two minutes.
You need a wallet on Robinhood Chain with a little ETH. Everything else is just the form.
Pick the repository
Type a name, an owner, anything — the search finds it the way X finds people. A library you use, a tool that saved you a week, your own project.
Name your token
A name, a ticker, a picture. The usual. Nothing here is special.
Sign twice
The launch itself, then a second, much cheaper signature that attaches the token to its repository — without it the token exists but nothing lists it, and its fees pile up uncollected. Budget 0.0005 ETH plus gas for the first and gas only for the second. You never hold the fee rights, so there is nothing for you to undo later.
Get a fee address
While you fill the form we quietly look for a mint address ending in fee. It takes a few seconds and costs nothing — a small mark that the token was launched here.
03 · If you maintain a repository
One file, and the balance is yours.
You do not need a wallet to be owed money — only to receive it. Add this to your default branch, with your own address:
{ "cofee": { "robinhood": { "ownedBy": "0xYourAddress" } } }
That file is the proof. Only someone who can write to the
default branch can put it there, and anybody can check it without
trusting us. We also read the drips key, so if you are
already set up with Drips you are already payable here.
Want the fees themselves, not just the balance? Once you have proved control, the vault can hand the token's fee stream directly to your address, for good. After that the money never passes through us again — and we could not take it back if we wanted to.
04 · Straight answers
The questions people actually ask.
Do I need the maintainer's permission?
No, and they are not notified. Anyone can point a token at any repository. Nothing is claimed on their behalf and nothing is signed in their name — a balance is simply held, and they can ignore it forever or take it tomorrow.
What if the repo gets renamed?
Nothing breaks. The money is booked against GitHub's numeric id, not owner/name. Renames and transfers do not touch it. The name on this site is only a label for the number underneath.
Can a balance expire?
No. There is no deadline, no dormancy rule, nothing in the contract that hands a balance back to us as time passes. That is a deliberate difference from the products this is modelled on.
My token is not listed.
It has to be declared against its repository — anyone can do it. It cannot be faked either: the factory asks pons who receives that token's fees and refuses unless it is that repository's vault.
A project wants out.
It comes off the site and we stop collecting fees from the tokens pointing at it. Anything already owed stays owed.
Where do the tokens trade?
On pons. Fixed supply of one billion, paired against ETH, sold from a bonding curve until it graduates into a Uniswap v4 pool with permanently locked liquidity.
05 · The uncomfortable part
Two things we would rather you knew now.
Published on purpose
The payout key could misbehave. No contract can read a file
on GitHub, so a human checks the proof and an operator key sends the
money. verser takes the destination as an argument —
that key could send a held balance anywhere, including to itself.
Both halves are readable in CoffreDepots.sol. What
makes it contestable is that every payout is published together with
the proof it relied on.
Almost nobody is reachable yet. Of the sixty most-starred repositories on GitHub, not one published a claim file when this was written. The file is something a maintainer adds after they hear money is waiting — it is not a pool of ready recipients. The contracts are also unaudited, and pons says the same of its own.
06 · Words
Four terms, in plain language.
Creator fee
The cut of every trade that a launchpad pays to whoever is registered as the token's fee recipient. On pons that recipient is a field of the launch.
The vault
A small contract, one per repository, that receives those fees and holds the repository's share. Its address comes from the repo id, so it can be computed before it exists.
A step
Balances are not dripped out. They are paid when they cross $5, then $10, $20, $50, $100, $250, $500, $1,000 — and every $1,000 after. The whole balance goes, not just the step.
ETH
The currency Robinhood Chain runs on, and the one tokens are launched against on pons. Fees are collected and paid in it, so nothing is converted and nothing is bridged. Payout steps are still counted in dollars, so a balance can cross a step and drop back under it as the price moves.
Check it yourself
None of this asks to be believed.
The factory, every vault and every payout are on Robinhood Chain, and each payout carries the proof it relied on.