Reference

Troubleshooting

Things that go wrong, what each one actually means, and the shortest way out. Almost none of them put money at risk, and this page says which ones do.

Launching

My wallet is not in the list

The list shows wallets that announce themselves through Wallet Standard, which Phantom, Solflare and Backpack all do. If yours is missing, unlock the extension and reload the page. If it still does not appear, update the extension: older versions announce themselves the old way, which the page only falls back to for Phantom, Solflare and Backpack.

A handle is refused

Either X says the account does not exist, which is usually a typo, or the handle was paid here before and now belongs to a different X account. The second case is refused on purpose: its fees would reach the previous owner. Check the handle on X and use the account’s current handle. If the message says X could not be asked, the lookup service is down for a moment and the handle has been paid here before, so it is not added on a guess. Try again in a minute.

The launch says it expired

The launch message has to be signed within 15 minutes of preparing. Nothing was spent. Prepare it again; you get a new creator address, and the old one is simply never used.

The name is too long for the transaction

A create with a first buy is close to Solana’s transaction size limit, and every byte of the name, ticker and metadata link counts. The page drops the optional compute budget instructions first. If it is still too large, shorten the name or remove the first buy.

The simulation failed

Most often the wallet does not hold enough SOL for pump.fun’s rent, the network fee and the first buy together. The message says what failed. Lower the first buy or add SOL. Nothing is sent until a simulation passes.

I signed, but the token is not on Explore

A token is listed only once its transaction is confirmed and the server has read it back. Go back to the launch page in the same tab: an unfinished launch is kept for the browser session and the confirmation resumes. If you cannot, wait a few minutes: a scheduled job looks for launches that were never confirmed, finds the token on chain and lists it. If the transaction never landed, your wallet was not charged for it. Check the signature on Solscan to be sure.

A launch whose transaction landed on chain still created the token on pump.fun, with the right creator address, and its fees accumulate in its own vault either way. The job only looks back seven days. For an older launch that is still not listed, send the signature to @slicepaddotfun and it can be rechecked against the chain.

Being paid

My balance is zero but the token trades

Fees reach balances only through sweeps. A token’s vault is swept once it holds 0.01 SOL, and the sweep job runs every few minutes. The token page shows what is in its vault now, so you can see fees on their way before they are credited.

I cannot sign in with X

Allow cookies for this site: the sign-in keeps its state in a short-lived cookie while you are on X’s consent screen, and needs it back afterwards. If you took longer than ten minutes on that screen, start again. If the page says sign-in with X is not available, it has not been configured on this deployment yet; your balance is safe and waits.

I signed in and see nothing

You are probably signed in with a different X account than the one that was named. Sign out on X, sign in with the right one, and try again. If you renamed the account, that is fine: the money is tied to the account, not the old handle. Your public page is at /x/<handle>.

My claim is refused

Below 0.01 SOL: that is the smallest claim.
A payout is already on its way: one at a time, so wait for it to land.
The address is not a wallet: paste the public address of a wallet you hold the keys to. Program-derived addresses, token and program accounts, the treasury, and the mints and fee addresses of tokens launched here are refused.
The address could not be checked: the chain did not answer just now. Try again in a minute.
Claims are paused: your balance is untouched and waits for the pause to end.

My payout is queued and not sent

Either payouts are paused, or the treasury would drop below its 0.05 SOL reserve by sending it. In the second case the operator is alerted, and payouts resume in order once the treasury is funded. The amount is out of your balance while it waits, so it cannot be claimed twice, and it returns to your balance if the payout fails.

My payout failed

A failed payout provably moved nothing: it either errored on chain or expired without landing. An expired payout is replaced by a new one for the same amount on a later run, so you may see a failed row followed by a queued or confirmed one; that is the same money, sent again. After three expired attempts, or an error on chain, the amount is back in your balance, and you can claim it again straight away. Autopay queues a new one on its next run.

I am on Burn and nothing has been burned

Burn orders for a token are pooled until they reach 0.02 SOL, then bought and burned in one run. A token with little volume can take a while to get there. The orders are already out of your balance and are counted as owed on the proof page until the buy lands.

When to worry

Only one situation on this page involves money that could be lost rather than delayed: a payout sent to an address you do not control. A transfer cannot be reversed, by us or by anyone. Everything else here is a delay, and the ledger and the proof page show whether the money behind it is still there.