Everything to ship, in one place. Fill in your coin once: get the metadata file, a launch thread and a checklist wired to the other tools. Template-based, no AI.
Fill it in once: the metadata file, the launch thread and the checklist links below are all built from these fields. Template-based and local — no model, no network call, nothing leaves this page until you copy or download it.
0 / 32 bytes
0 / 13 bytes
Plain text. The pin step trims it; the program does not limit this field. It goes into the metadata file verbatim.
Required by the pin step, which fetches this URL and re-hosts the image on IPFS — so it has to be a link a server can read, not a file on disk.
Left empty, the key is left out of the metadata file entirely.
Left empty, the key is left out of the metadata file entirely.
Left empty, the key is left out of the metadata file entirely.
the mint the Grinder produced, or any base58 mint address
Not part of the metadata file — it is a buy, not a field. It appears in thread post 2 and is what you type into the Launch Lab.
Why the contract address is not prefilled
The shape src/lib/pinata.ts writes when it pins, minus the showName: true that the pin route adds itself. An optional key with no value is left out rather than written as an empty string.
{
"name": "",
"symbol": "",
"description": "",
"image": ""
}Upload this file to IPFS (or a pinning service) or let the Launch tab pin it, and the URI that comes back is the uri of the create transaction. The image URL above is pinned separately, and the metadata file points at the IPFS copy of it.
A template, not a model: every line below is your fields with fixed wording around them, and a post that has nothing to say is left out. X allows 280 characters per post on a standard account — the counter is Unicode code points, which is how X counts them.
Nothing to write yet — the thread needs at least a name and a ticker.
Left out of the thread — nothing was invented to fill the gap
Nine steps, each linked to the tab that does it. A tick appears only where this page can read real state — the launch registry for the last two, a read-back of the pinned file for item 7. Anywhere the app keeps no record, the item says not tracked here instead of offering a checkbox that does nothing.
Grind your CA — not tracked here
The Grinder generates its keypair in that tab's memory and stores nothing — no localStorage, no cookie, no server record — so this page cannot see whether you ground an address, and it cannot prefill the field either.
Check your Vamp Shield score — not tracked here
The score is computed in the Shield tab and nothing is written back, so this page cannot tick it. The link picks up the contract address above as soon as there is a valid one.
Back up the mint key (Vault or offline file) — not tracked here
The Vault holds the platform's treasury key server-side and never shows a private key; the mint key you ground lives only in the Grinder tab. Whether you saved it is not recorded anywhere this page can read.
Simulate your dev buy and wallets — not tracked here
The Launch Lab is client-side arithmetic on the bonding curve and writes nothing down, so there is no result here to read.
Set creator-fee splits — not tracked here
The Splits tab validates the split to 10,000 bps and it is written on chain at launch — not stored in this browser, so this page cannot tick it. The link carries the contract address above once there is a valid one.
Pin the metadata — not tracked here
The pin runs on the Launch tab, which prints the resulting URI in its build log and keeps no record this page can read. Paste that URI into item 7 below and the pin gets checked here for real.
Check the pin landed — not checked yet
Paste the metadata URI from the Launch tab's build log and press check: this page fetches it back through your browser, and the tick only appears if the pinned JSON comes back with this coin's name and ticker.
ipfs://<cid>, a https gateway URL, or a bare CID.
Launch or hand over to the platform treasury — not checked yet
The registry is written by the launch path only after a transaction confirms — a planned launch is never recorded. Press check the board to read it.
Import it on our own board — not checked yet
The board renders exactly what the registry holds, so the same record that answers item 8 answers this one: it is on the board when it was recorded there.
The Launch tab takes this coin the rest of the way: it pins the image and the metadata file, builds the create against the real pump.fun program, simulates it, and only then asks for a signature. Come back here when a field goes red — the byte counts above are the same ones the create instruction applies.
This build prepares and simulates only: NEXT_PUBLIC_ENABLE_SEND is not "true", so nothing can be submitted from any tab — the safe default.