Capital flow
What happens between a trade and a repository.
Trading fees accrue to the vault named as the token's fee recipient on pons. They are withdrawn on a schedule, and the repository's share is held for it in ETH — the currency the chain itself runs on — so there is no conversion step and no bridge in between. What a repository is owed therefore moves with the price of ETH.
01 · The route
Five steps, and the money only moves on the last one.
Everything before the payout is bookkeeping: the fee is credited, then booked. Nothing leaves the chain, and nothing is converted.
- pons curve or poolEvery trade pays a creator fee
- Fee escrowCredited by pons, not pushed out held by pons
- The repository's vaultBooked to a numeric repo id
- A maintainer proves controlA commit on the default branch FUNDING.json
- Paid in ETHConfirmed in public, on chain payout
02 · The split
Move the slider, and watch the fee split.
A fee is not a payment. Between the trade and the repository it changes hands twice, and both hands are contracts. The two rates below are read from the deployment, not written into this page.
Traded
$0
Volume on the token
Creator fee
$0
— of every trade
Held for the repo
$0
— of the fee
A model of the mechanism, not a forecast: it shows how a fee is split,
never how much a token will trade. The share is a constant in the
vault contract, PART_DEPOT, and it cannot be changed for
a token once it is launched.
03 · Guarantees
What the vault guarantees.
Four properties written into the contract, and that anyone can read there.
It is named inside the launch
pons takes the fee recipient as a field of the launch itself, so the vault holds those rights from the first block. The launcher never held them and cannot undo it. CO-FEE's operator key can still hand the stream over — that is published, not prevented.
It books to an id, not a name
A repository can be renamed or transferred. The balance is held against GitHub's numeric id, which does not change.
Nothing expires
No expiry and no dormancy rule: time alone never returns a balance to us. But the payout itself is sent by CO-FEE's operator key, which names the destination — read CoffreDepots.sol rather than take our word for it.
It can hand the stream over
Once a maintainer has proved control, the vault can pass the token's fees directly to them, permanently. After that the money never reaches us again.
04 · The limit
What it does not guarantee.
The weakest link, published on purpose
The contract guarantees the accounting and the publication, not that the right person is paid. Nothing on chain can read a file on GitHub, so a human checks the commit that proves control, and the proof is recorded with every payout so anyone can dispute it. Until someone claims a repository, its balance simply waits — with no deadline.
05 · The record
Payouts sent.
Every payout, with the repository it reached and the date of the proof it relied on.
Check it yourself
Nothing here asks to be believed.
The factory, the vaults and every payout are on Robinhood Chain, and the proof each payout relied on is published with it.
CO-FEE is not affiliated with GitHub, Inc. or with any project listed here. The repositories on this page have not approved, endorsed or requested anything, and their maintainers have not been asked. Anyone can launch a token and point its fees at any repository, which is exactly what this page shows. A repository is paid only once someone who controls it proves so, by committing a claim file to its default branch. If a project would rather not be listed, it comes off the site and CO-FEE stops collecting the fees of tokens pointing at it, while any balance already owed stays owed, with no deadline and no expiry.