What to Do When a pump.fun Launch Fails

You pressed launch and something is wrong. Maybe the button spun and came back with an error. Maybe the project page says the launch did not go. Maybe the coin exists but one of your wallets has no tokens. Before you touch anything, take a breath, because the single most expensive move after a failed launch is pressing launch again without knowing what happened.

#First question: did anything land?

Every useful diagnosis starts here. Open your wallets and look at balances, and look for the coin itself.

1. Nothing sent

   the pre-send check stopped it, balances unchanged

2. Bundle dropped

   sent but not picked up, nothing on chain

3. Coin exists

   bundle landed, so every buy in it landed too

4. Partial

   only possible on devnet, where transactions go one by one

On mainnet, a launch is one Jito bundle. Bundles are atomic: every transaction lands, in order, in the same block, or none do. So on mainnet there are really only two outcomes once something is sent. Either the coin exists and all your launch buys are in it, or nothing exists and nothing was spent. That makes diagnosis much simpler than it feels in the moment.

#Failure type 1: the pre-send check stopped it

Right before sending, DevBundler runs one fast check. It confirms that:

• pump.fun is reachable,
• the coin address is unused,
• every wallet has enough SOL for its buy and costs,
• the buys will not sell out the whole bonding curve.

If any of those fail, nothing is sent. The project page shows the reason and a "Launch again" button.

This is the most comfortable kind of failure. Nothing happened on chain and you have a specific reason.

#Failure type 2: the bundle did not land

The check passed and the bundle went out, but no coin appeared. On mainnet, that almost always means the bundle was not picked up by a block builder before its blockhash expired. The usual reason is a tip that was too low for how busy the network was.

Because the bundle is all or nothing, nothing in it executed: no create, no buys, no tip, no fees. Your wallets should show the same balances as before. Confirm that, then:

1. 1

   Confirm balances

   Every wallet should hold what it held before you pressed launch.

2. 2

   Confirm no coin

   Search for the coin to make sure it was not created.

3. 3

   Raise the tip

   We suggest at least 0.005 SOL in normal conditions; go higher when the network is busy.

4. 4

   Raise the priority fee

   It helps transactions get scheduled when the network is congested.

5. 5

   Check the dev wallet

   It pays the tip. Make sure it still covers everything at the new level.

6. 6

   Launch again

   With the same details, since the coin was never created.

Tip levels change constantly, so do not treat any number as fixed. Jito tips explained covers how to judge it on the day.

#Failure type 3: the coin launched, but not how you planned

If the coin exists, the bundle landed. On mainnet, that means every buy in it landed too. So if the numbers look off, the cause is usually the plan, not the launch.

• Your combined share is higher than you expected. The buys were bigger than intended, or there were more wallets than planned. The launch table estimated this; compare it with what you see.
• Later wallets got fewer tokens. That is how the bonding curve works. Every buy raises the price, so equal SOL gets fewer tokens each time.
• You see buyers right after yours. Bots and traders can buy in the blocks after your bundle. A bundle stops anyone buying between your wallets, not after them.

None of these are reversible. A landed mainnet bundle is final.

#The error codes you will see

pump.fun's program returns numbered errors. Three cover most of what goes wrong around launches and trades.

6002 and 6003 are slippage failures. The price moved between the quote and the moment the transaction executed, beyond the allowed tolerance. They are common when several wallets trade at once against the same price. DevBundler quotes every wallet in a batch in order, so each later wallet's minimum accounts for the earlier ones, which keeps those limits reachable. If you still hit one, retry with a fresh quote, or a slightly wider slippage when the market is moving fast. Slippage on pump.fun explained has more.

6005 means the curve has completed. Once 79.31% of supply has sold, the coin migrates to PumpSwap and the curve refuses buys. On mainnet, DevBundler blocks launches whose own buys would sell out the curve, and after migration its trading switches to PumpSwap automatically.

#The devnet exception

Devnet has no Jito. A devnet launch sends the create and the buys one after another, so it can partly succeed: the coin is created and some buys fail.

#Before you retry anything

If you keep running into the same problem, common pump.fun launch mistakes lists the usual suspects, and the full flow is in how to launch a pump.fun coin with a bundle.