Ponspree
$PSPREE · ROBINHOOD CHAIN 4663

Launch a coin from the tweet you're reading.

Two buttons on every post on X. One reads the tweet, names the token and launches it in a single click. The other opens a form first. No wallet to connect, no popup to confirm.

56 assets to pair against ~$5.20 a launch ~1.7s tweet to signed Tokens launch on pons v2

Pair with ETH — or with a tokenised stock. Graduation threshold shown.

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.

pons charges 0.0005 ETH to launch. That is the small part. The launch itself burns 3.5–5.6 million gas, so a realistic budget is around 0.003 ETH — about $5.20 at the time of writing. 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.

Operation Gas At 0.41 gwei
ERC-20 transfer 65,000 $0.07
pons launch 3,700,000 $4.10
launch + first buy 5,600,000 $6.20

It is not congestion. Base fee sits at 0.41 gwei, 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.

2,695,400 — storing contract bytecode ~1,000,000 — constructors, storage, pool setup

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.

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. Send it a little ETH on Robinhood Chain and you are live. Back up my key and Import a key are both in settings; nothing is held on a server.

Set a password and the key is sealed with AES-GCM under a PBKDF2-SHA256 key at 600,000 rounds. 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:

Signs
launchToken · launchAndBuy

The pons factory and the launch router. Nothing else is a launch.

Signs
approve(router, amount)

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.

Signs
sweepFees · claim

Collecting your creator fees. Both pay whoever calls them, so there is no recipient to redirect — money only moves towards you.

Refuses
any other destination

There is no path that sends ETH to an address of someone else's choosing. Even with full control of the page.

Refuses
a launch over your spend cap

Checked against stored settings, so the page cannot raise its own limit. 0.05 ETH by default.

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
Ask me first off Off means one click really launches. Nothing can be undone afterwards.
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 0.05 ETH A launch costing more is refused before it is signed.
Lock after 60 min Idle minutes before the wallet re-locks. It always locks when the browser closes.
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 none Pins the logo to IPFS. Without it the token points at the picture's own URL.

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

Chrome only installs extensions from its own store, and Ponspree is not there yet — so this is the download-and-load route. It works in Chrome, Brave, Edge, Arc and anything else built on Chromium.

Download Ponspree .ZIP · 290 KB · CHROMIUM BROWSERS

Then, once:

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

A wallet is made for you straight away. The popup shows its key once and asks you to save it — do that before you send it anything. Then set a password and give the address a little ETH.

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.