Coming soon on Robinhood Chain, powered by Pons
Every commit
is a buyback.
Launch a coin for any GitHub repo. Every push to its default branch spends a slice of the coin's vault buying it back, then burns what it bought. The chart moves when the code does.
- trigger
- git push
- per commit
- % of vault
- bought
- burned
Replay any repo.
Pick a public repo. We pull its real latest commits from GitHub and replay them as if its coin were live. Simulated numbers, real commits.
- commits
- 0
- vault
- 0.0000 ETH
- bought back
- 0.0000 ETH
- burned
- 0
Starts from a 1 ETH vault. Each commit spends % of what's left. Not live data.
Every square is a buy.
A year of commits for the replayed repo. On Commit, each one is a buyback.
How it works
A coin names a repo. Its vault fills from trading fees. Each commit spends a slice of the vault on the coin, then burns it.
-
1
Pick a repo
Paste any public GitHub repo. The coin is tied to it for good: its default branch becomes the trigger.
-
2
Launch on Pons
A standard Pons coin: bonding curve first, then a locked Uniswap v4 pool. Creator fees are split: % to the repo's buyback vault, % to Commit.
-
3
Code ships, chart moves
Our keeper watches the branch. A new commit lands, % of the vault buys the coin on its pool and the tokens go to the dead address. Every buy is on the chart.
One rule, written down.
No votes, no roadmap promises. The repo's commit history is the only input. If the code moves, the coin gets bought.
- Only the default branch counts. Pushes to other branches do nothing.
- A merge counts once. Force-pushed or rewritten commits never count.
- Each buy is a share of what's left, so spamming commits only splits the same vault into smaller buys.
- At most one buy every minutes per coin. Commits in between are batched.
# what happens on every push
trigger = push to default branch
per_commit = % of vault
cooldown = min, then batch
buy_on = the coin's Pons pool
send_to = 0x000000000000000000000000000000000000dEaD
# fees, every trade
vault = %
commit = %
Where the money goes
Fees only ever go two ways: into the repo's vault, or to Commit. The vault has one job: buy its own coin and burn it.
For launchers
Back the code you believe in.
- Launch for any public repo in under a minute.
- Pick your coin's name, ticker and image yourself.
- Add a dev buy in the same transaction.
- Pick a repo that actually ships. That's the whole game.
For holders
Watch the commits, not the hype.
- Every buyback links the commit that triggered it.
- Burns are on-chain, sent to the dead address.
- An active repo means steady buys. A dead repo means none.
- The vault keeps filling as long as the coin trades.
Questions
Do the repo's maintainers have to do anything?
No. Commit only reads public commit history. Maintainers don't sign up, hold anything or even know the coin exists. A coin doesn't mean they endorse it.
What counts as a commit?
A new commit that reaches the repo's default branch (usually main or master). A merged pull request counts once. Commits on other branches, and history that gets force-pushed away, don't count.
What stops someone from spamming commits?
Each buy spends % of what's left in the vault, so a hundred empty commits just split the same money into smaller buys. Buys are also spaced at least minutes apart per coin.
Where do the fees go?
% of each coin's creator fees fill its repo vault, which only buys back and burns that coin. % go to Commit.
What if the repo goes quiet?
No commits, no buys. The vault keeps what it has and spends it when the next commit lands.
Which chain?
Robinhood Chain. Coins launch through Pons, so they trade on Pons and on a locked Uniswap v4 pool after the curve.
When does it open?
Soon. Follow Commit on X for the launch.