A good Pump.fun launch checklist covers four areas before any order runs: a finished token page with image, description and working links; live socials with a pinned plan for the first hour; a named person answering comments; and the session itself, meaning a fee wallet you control, a sized target and length, your comment lines, and a mint address checked twice.
Ready means
- A visitor landing on the coin page finds an image, a clear description and links that open.
- Someone specific owns the comment thread and the socials for the first hour, with a backup.
- The fee comes from a wallet you control, and nothing in the process asks for your keys.
- The mint in the console matches the mint on the coin page, checked twice.
What does the full checklist look like?
Work through it in order. Items near the top take the longest and are the hardest to change once the coin is live; items near the bottom take minutes and belong on launch day.
- Final token image: square, legible at thumbnail size.
- A two or three sentence description that says plainly what the token is about.
- Website, X account and Telegram or Discord links, each opened and tested.
- Socials with a few posts already up, so new visitors do not land on an empty profile.
- A pinned first-hour plan on your main channel.
- A named person who answers comments on the coin page, plus a backup.
- A wallet you control holding the fee plus a little SOL for the network fee.
- A decided target volume, order band and session length.
- A comment approach: built-in library and language, or your own .txt file.
- The mint address, checked twice against the live coin page.
Is the token page ready for visitors?
The coin page on Pump.fun is where session activity sends attention, so it has to hold up when people arrive. The image, name, ticker and description are set when the coin is created; in practice, treat them as fixed once it is live and finish them first.
The description should answer one question: why does this token exist? Two or three plain sentences beat a paragraph of slogans. Then open every link from a phone. A dead Telegram invite or a website that times out wastes exactly the attention the session brings.
Socials need a few posts before launch, a profile image that matches the coin, and a bio that links back to the coin page.
Who is on duty during the first hour?
Write a short pinned post for your main channel: when the session starts, what the community can expect to see, and where to ask questions. Keep it to what you control, such as timing and links, and leave out anything about price.
Then name owners. One person answers comments on the coin page; another posts updates on socials. Session comments come from distinct wallets at the density you choose, but replies from the team give the thread a voice no library can. On a small team one person can cover both, as long as breaks are planned so the thread is never left alone for long.
Which wallet pays the fee, and what does it need?
Use a wallet you control and can sign from. PumpCrest never asks for a seed phrase, a private key or a wallet connection; the only transaction is your own fee transfer to the payment address the console shows. You do not send trading capital, so the wallet only needs the fee plus enough SOL for the network fee on that one transfer.
The mint does not have to be yours. Any public Pump.fun mint works, so a community member or partner can fund a session for a coin they did not create. Agree on it in advance so the team is ready when activity starts.
How big and how long should the first session be?
Start from the PumpCrest presets and adjust. First hour uses 500 wallets on a 0.10 to 0.30 SOL band for 60 minutes. The average order is 0.20 SOL, so the target is 500 x 0.20 = 100 SOL, exactly the 100 SOL minimum, and the fee at 1% is 1 SOL. Expect about 800 orders and an estimated 310 unique holders, based on the console estimate of about 62% of wallets.
For a longer window, Slow build runs 1,200 wallets at 0.10 to 0.40 SOL over 3 hours: a 0.25 SOL average, a 300 SOL target and a 3 SOL fee. Matching length to your team's availability matters as much as the number, and the session length guide covers that trade-off, while choosing a start time has its own guide.
If the coin is close to completing its curve, read the bonding curve progress on the live page before choosing a length. Execution follows the token into its pool if the curve completes mid-session, so a longer run is not wasted, but it changes where the activity shows up.
When should each item be done?
| Item | Why it matters | When to do it |
|---|---|---|
| Token image and description | The first thing visitors judge, and hard to change later | Before creating the coin |
| Website and social links | Dead links waste the attention a session brings | Before creating the coin |
| Social posts and bio | Empty profiles look abandoned | 2 to 3 days before |
| Comment lines (.txt) | Lines that fit the token read better than generic ones | 1 to 2 days before |
| Pinned first-hour plan | Tells the community what to expect and where to ask | The day before |
| Comment owner and backup | A thread with no team replies reads as unattended | The day before |
| Target, band and length | Sets the fee and the shape of the tape | The day before |
| Fee wallet funded | Payment is the only step you sign | Launch day, before opening the console |
| Mint checked twice | A wrong mint cannot be undone once the session starts | Launch day, right before paying |
Should you write your own comment lines?
The built-in library covers eight languages: English, Chinese, Korean, Japanese, Spanish, Portuguese, German and Russian. Pick the one your community actually writes in. If the token has a theme, an inside joke or a specific story, your own lines will fit it better than any library.
Upload a plain .txt file, one line per comment, up to 512 KB; it is read in the browser only. Size the file to the session: at 15% density on about 800 orders, roughly 120 comments are posted, so write at least 150 lines to keep repeats low. That is still tiny, since 200 lines of about 80 characters come to around 16 KB.
- Write in the voice of a holder, not a press release.
- Mix short reactions with a few longer lines about the token theme.
- Leave out price predictions and promises; they invite the wrong replies.
- Read the file aloud once. Anything that sounds odd will look odd in the thread.
How do you confirm the mint before paying?
Copy the mint from the live coin page, never from a chat message or a screenshot. Paste it into the console, where PumpCrest reads the public metadata, name, ticker and image, so you can see it is the right coin. Then compare the first four and last four characters with the coin page a second time.
Copycat coins with similar names and images do appear, and the fee is not refundable once a session has started. Thirty seconds here protects the whole session.
Save the project in the console after paying. Saved projects list each order as awaiting payment, running or finished, which keeps launch-day status in one place.
Questions and answers
How early should I start preparing?
Three days is comfortable for a first launch. That leaves a day to finish the image and description, a day to build up socials and write comment lines, and a day for the pinned plan, roles and sizing. Payment and the mint check belong on launch day, because they take minutes and depend on the coin being live.
Do I need a separate wallet for the fee?
It is a good habit. A wallet used only for launch costs keeps your records clean and makes the Solscan link the console shows easy to match to the session. Pick one you control and sign from directly, such as a regular Solana wallet app, rather than an exchange account where the sending address is not yours.
What if the image or description is not final on launch day?
Wait. The session sends attention to the coin page, and an unfinished page turns that attention away. Because those details are set at creation and are hard to change once the coin is live, they sit first on the list for a reason. A one-day delay costs nothing; a session pointed at a half-built page costs the whole fee.
Which language should the comments use?
Match the language your community uses on socials. A Korean community reads Korean lines naturally and skims past English ones, and the reverse holds too. If your audience is mixed, a custom .txt file lets you blend languages in the proportion you see in your own channels, which no single library setting can do.
Should the first session be large to make an impression?
Not necessarily. A first session shows how your community responds, how the thread feels at a given density and how holders build. The First hour preset at the minimum costs 1 SOL and gives you that data. A second session sized from what you learned tends to use the budget better than one oversized first run.
Checklist done? Open the console
Paste the mint you checked twice, pick the preset closest to your plan and read the fee before you pay. Nothing to install and no wallet connection needed.
We build the PumpCrest console and write these guides from the operator side: what a session spends, what settles on-chain and what a visitor sees on the board. Corrections are welcome at support@pumpcrest.com.