Install Plugin
Top launches
Biggest by market cap, priced off their own curves
Reading the chain...
Newest
Every launch made with Ponspree
Reading the chain...
How a launch works
From click to signed transaction, without leaving the timeline.
It reads the post
Text, author, permalink, and the picture - the first image, a video's thumbnail, or the poster's profile picture when the post carries no media of its own. The tweet's link is written into the token's X field on-chain.
Claude names it
Claude Haiku 4.5 reads the post and its picture and returns a name, ticker and one-line description. Roughly a fifth of a cent per launch, and there is no key to add - naming is built in. If the model can't be reached, the name comes from the tweet's own words rather than blocking the launch.
The launcher wallet signs
While Claude is naming, the extension is already reading the chain - fee, economics, gas, balance. The transaction is built and signed locally. A first buy rides inside the launch, so you are never sniped on your own token.
Pairings
The part that has no equivalent anywhere else.
A token can trade against ETH, or against any of the tokenised equities pons has approved - Apple, NVIDIA, Tesla, GameStop, SpaceX, and fifty-odd more. Pair a memecoin with GME and it graduates when the curve has raised 369 GME, not ether.
The list is rebuilt from the factory's own approval events rather than hardcoded, and refreshes itself every six hours - a stock pons adds shows up without a new build. Each asset carries its own graduation threshold and its own decimals; USDG has six, cbBTC has eight, and a first buy is denominated in whatever you paired against.
Paying a first buy in stock
A stock-paired first buy is pulled by the router, so it needs an allowance before the launch will go through. The extension notices and signs both transactions, in order - you see one action.
What it costs
Measured on-chain, not quoted from the docs.
Robinhood Chain is cheap. Gas has been sitting under 0.1 gwei, which puts an ordinary token transfer around a penny. So the first thing to say about a launch costing a couple of dollars is that it is not the chain being expensive.
pons charges 0.0005 ETH to launch - about $1.25 - and Ponspree charges 0.0001 ETH, about $0.25, all of which buys $PONSPREE and burns it. The rest is gas, and there is a lot of it by unit count: a launch burns about 3.6 million, roughly fifty-five transfers' worth. Budget 0.001 ETH and you have room to spare. Every figure the extension shows you counts gas; quoting the fee alone is how a wallet ends up funded to 0.002 and reverting with no reason given.
Gas units are the stable part of this and the only part we control. What a unit costs, and what ETH is worth, both move - so the dollar figures here are indicative and the panel on your own timeline is the one to trust. It prices each launch at the moment you are about to make it.
Keep a little more than that in the wallet. The chain makes an account cover the maximum a launch could use before it will accept the transaction, then refunds whatever went unspent - so the hold is around 15% above the bill, and the difference comes back. The extension quotes you the bill and only mentions the hold when it is the reason a launch is being refused.
| Operation | Gas | At 0.07 gwei |
|---|---|---|
| ERC-20 transfer | 65,000 | $0.01 |
| pons launch | 3,650,000 | $0.63 |
| launch + first buy | 3,800,000 | $0.65 |
It is not congestion either. Base fee is flat and blocks run at effectively zero utilisation - the chain is idle. The cost is what a launch does: it deploys the token, its bonding curve, and initialises a Uniswap v4 pool, all in one transaction. The gas price is tiny; the number of units is not. That is the whole of it.
73% of a launch's gas is spent writing the same two contracts to the chain again. The token is 3,248 bytes and its curve 10,229 - byte-for-byte identical on every launch, paid for every time. Minimal proxies would cost 18,000 gas instead of 2,695,400, taking a launch to roughly $1.50. That is a pons design choice, not a chain limit.
You do not have to take any of this on faith. A panel sits in the corner of your timeline with the live bill on it - pons's fee, the network's gas, your first buy, ours, the total in dollars, and what your wallet holds against it. It updates as gas and the ETH price move, and it is there so you can check it rather than believe it.
Ponspree charges 0.0001 ETH a launch - about 25 cents, roughly a tenth of what a launch costs and a fifth of what pons itself takes. It is a line on that panel like every other, above the total, never folded into the gas figure. Priced in ETH rather than dollars so it is a fixed number you can check on-chain rather than whatever a price feed said at the time, and it is sent only after a launch has actually landed - a launch that reverts is not charged for.
All of it buys $PONSPREE and burns it. Not a share, not after costs: every fee this collects goes back into the token and is destroyed. Actioned each time platform revenue passes $1,000 - about four thousand launches - and done by hand rather than by contract, which is deliberate: a contract standing between you and your launch is one more unaudited thing holding other people's money, and this does not need one to work.
Doing it by hand means it has to be checked rather than trusted. The wallet below is the only place fees land, and every buy and every burn leaves a transaction anyone can follow from it.
The wallet it collects into is 0x47bCa515…83f0, so what has come in and what has gone back out are both on the chain. What you are taking on trust is that it keeps happening. A contract would enforce it and a promise does not, and we would rather say that than imply otherwise - but the wallet is public, so the promise is one anybody can hold us to rather than one you have to believe.
The wallet
Made for you on install. It is the only wallet the extension uses.
There is nothing to connect. The extension generates a key, holds it locally, and signs every launch with it - which is what makes one click actually launch. Back up my key and Import a key are both in settings; nothing is held on a server.
Getting ETH onto it. Robinhood Chain is an Arbitrum chain, so the canonical bridge is the route its own documentation points at: portal.arbitrum.io. Pick Ethereum as the source and Robinhood Chain as the destination, and leave yourself enough on mainnet to pay for the deposit. It lands in about ten minutes. Faster third-party routes exist and charge for the privilege; the canonical one is trustless and inherits its security from Ethereum.
0.01 ETH covers a good few launches. The extension shows you its own address and this same link the first time you open it with an empty wallet, so there is nothing to write down from here.
The password is set before the wallet exists, and the key is sealed with AES-GCM under a PBKDF2-SHA256 key at 600,000 rounds. That order is the point: a key is generated only at the moment there is a password to encrypt it with, so there is never a window where an unencrypted one is sitting in a browser profile. The decrypted copy lives in session memory only - gone when the browser closes, and out of reach of any page. You unlock once per session, not once per launch.
Because it signs without asking, the guards are in the service worker where no page can reach them. What the wallet will and will not put its name to:
The pons factory and the launch router. Nothing else is a launch.
Only on a token pons has approved, spender pinned to the router, carrying no ETH. The one non-pons transaction it will put its name to.
Collecting your creator fees. Both pay whoever calls them, so there is no recipient to redirect - money only moves towards you.
There is no path that sends ETH to an address of someone else's choosing. Even with full control of the page.
Checked against stored settings, so the page cannot raise its own limit. There is no cap unless you set one - the settings table below says the same.
What the guards don't cover
Without a password the key sits in the clear in your browser profile, and anything that can read the profile can take it. The guards bound what the extension will do, not what someone holding the key can do. Set a password, keep the balance small.
Settings
Everything the buttons do is configured in the extension, from the toolbar icon. Settings live in the extension's own storage - a web page cannot reach them, and that is deliberate.
| Setting | Default | What it does |
|---|---|---|
| Paired with | ETH | What your tokens trade against and graduate in. |
| Your first buy | 0 | Bought inside the launch transaction, so nobody snipes you. |
| Spend cap | none | Set one and a launch costing more is refused before it is signed. 0 means no limit. |
| Lock after | 0 | Idle minutes before the wallet re-locks. 0 stays unlocked until the browser closes, which it always does. |
| Creator wallet | yours | Where creator fees land. Blank uses the launcher wallet. |
| Creator tax | 0% | Your cut of trades on top of the 1% base fee. Capped at 10%. |
| Pinata JWT | not needed | Every launch already gets a permanent copy of its picture on IPFS, stored by us. Add a key of your own and the copy lands in your Pinata account instead. |
Settings also keeps a record of everything you have launched - logo, ticker, the tweet it came from - alongside what pons is holding for you in fees, with a button to collect it. Before a token graduates its fees sit on its own bonding curve and are moved to the escrow first; after graduation it is a single step.
Install
Ponspree is on the Chrome Web Store. One click, and it updates itself from then on. It works in Chrome, Brave, Edge, Arc and anything else built on Chromium.
Either way, the first thing it does is ask for a password, then make the wallet and show you its key to write down. The password is not optional and comes first: a key is generated only at the moment there is something to seal it with, so one never sits unencrypted in a browser profile waiting for someone to get round to it. After that it hands you the address to fund.
Installing the zip by hand
The same extension, loaded yourself. It is here because the store does not serve everyone: a listing is not distributed in the EEA while we are registered as a non-trader. Loaded this way it will not update itself, so come back for a new one.
Unzip it
You get a folder called ponspree. Keep it somewhere you won't delete
- the extension runs from it.
Open chrome://extensions, turn on Developer mode
The toggle is in the top right of that page.
Load unpacked, and pick that folder
Chrome reads the extension from where that folder sits, so moving or deleting it later removes the extension - and with it the wallet, if the key was never written down. Then open the popup and it takes you through the password.
Before you fund it
pons v2 is deployed but not finished being audited - three firms are reviewing it and none have published. Liquidity locks permanently at graduation; there is no unlock. And anyone can launch a token with any name or image: launching from someone's tweet does not make it theirs, and the token address is the only identifier that cannot be copied.