The Most Common Mistakes When Launching Your Own Token on Solana

Creating a token on Solana takes a minute and costs a fraction of a SOL. That is exactly why most launches fail not at creation but around it: in settings nobody double-checked, in the pool, in the first minutes of trading and in promises made to buyers. Solidus Labs found that about 98.6% of tokens created on Pump.fun between January 2024 and March 2025 ended up with less than $1,000 of liquidity (Solidus Labs, May 2025).

Almost every mistake below is visible on-chain, so scanners, aggregators and experienced buyers spot it within minutes. We grouped them into technical, launch and legal mistakes, with the consequence and the fix for each.

#Checklist: mistake, consequence, fix

#Technical mistakes

#1. Leaving mint or freeze authority active

The most common mistake. An active mint authority lets the owner print new supply, and an active freeze authority lets the owner lock any holder's account. RugCheck shows both as danger-level risks, Jupiter's API marks them as risky, and Meteora DLMM and Orca do not give a freezable mint a pool without review. We covered this in detail in What Are Mint and Freeze Authority on Solana? In short: for a memecoin or community token, revoke both at creation.

#2. Mutable metadata and fragile logo hosting

While metadata is mutable, RugCheck shows a "Mutable metadata" warning and Phantom marks the token as mutable. That is a softer signal, and some teams keep it on purpose to fix links. The other half of the problem is hosting: if the URI goes offline, wallets cannot show the token's metadata, so Solana's docs advise permanent storage such as Arweave or IPFS (Solana docs). Storage services change too: NFT.Storage Classic stopped accepting uploads on June 30, 2024 (notice).

Use a square logo in a common format, keep the JSON and image on durable storage, check them in several wallets, and only then make the metadata immutable: after that, a broken link can never be fixed.

#3. Wrong decimals or supply

Decimals are set when the mint is initialized, and the token program has no instruction to change them later. The raw amount (supply × 10^decimals) must also fit into a u64, whose maximum is about 1.8 × 10^19: with 9 decimals that is roughly 18.4 billion whole tokens, with 6 decimals about 18.4 trillion. Pump.fun coins use 1,000,000,000 tokens with 6 decimals, a de facto memecoin standard. A quadrillion tokens with 9 decimals cannot be minted at all, and 0 decimals makes small trades impossible.

#4. Risky Token-2022 extensions

Token-2022 is a good default as long as extensions stay minimal. Most extensions cannot be added after the mint is created (Solana docs), and DEXes accept only some of them without permission:

Sources: Raydium, Meteora, Orca.

A transfer fee costs twice. Traders pay it on top of the pool fee on every swap, and whoever holds the fee-config authority can raise it, up to 100% at the program level, effective two epochs later (Solana docs). RugCheck flags that as "Fee config enabled". A permanent delegate, which can move or burn tokens from any account, is even worse for trust.

#5. Choosing the wrong pool type

On Raydium, the docs recommend CPMM for new constant-product pools and tokens with unknown price discovery: a 0.15 SOL creation fee, fee tiers of 0.01%, 0.25% and 1%, Token-2022 and Burn & Earn support. Legacy AMM v4 also costs 0.15 SOL but takes only SPL Token mints and cannot be used with Burn & Earn. CLMM earns nothing when the price leaves your range and is not recommended for price discovery (Raydium fees). Meteora DAMM v2 adds fee schedulers that start high and decay, designed against snipers, and positions that can be locked forever while still earning fees (Meteora).

#6. Too little liquidity and a careless opening price

The opening price is simply the ratio of your first deposit. Raydium advises setting it close to the market, since arbitrage rebalances a mispriced pool at your expense, and warns that very small pools give bad price impact (Raydium guide). How bad, by our calculation:

#7. Not locking or burning the LP

If the LP tokens stay in the creator's wallet, the liquidity can be pulled at any moment. RugCheck shows "Large Amount of LP Unlocked" as a danger, and Jupiter's verification looks at locked liquidity. Solidus Labs found a "soft rug" liquidity-sweep pattern in about 93% of roughly 388,000 Raydium AMM v4 pools it studied. The fix is Raydium Burn & Earn, which locks the LP forever while a Fee Key NFT keeps collecting fees (CPMM and full-range CLMM only), or a permanently locked Meteora DAMM v2 position. Pump.fun burns the LP itself at migration.

#8. Hot keys and expired transactions

Deploy from a fresh, dedicated wallet, keep the treasury and LP away from your trading wallet, and move any authority you keep into a multisig such as Squads. Do not let a launch transaction sit in the wallet: a blockhash is valid for 150 blocks, roughly 60–90 seconds, and an expired transaction is never processed (Solana docs).

#Launch mistakes

#9. Sniping and bundled launches

A team can create a token and buy it in the same instant: Jito bundles execute up to five transactions in order and atomically in one slot (Jito docs). Bots do the same from the other side, and on-chain analysts see both. Bubblemaps defines a bundle as wallets that bought together at launch and calls a bundle holding 10% or more of supply a major red flag (Bubblemaps, May 6, 2026).

In December 2024, Bubblemaps flagged a team-linked cluster that at one point held 96% of the HAWK supply. The team said it had tried to stop snipers with high launch fees on Meteora and denied selling; the token fell more than 90% from its peak (The Block).

Do not buy your own launch from many fresh wallets: that is exactly what scanners call a bundle. Use anti-sniper fee schedules or an Alpha Vault, where users deposit before launch and the vault buys in a protected window.

#10. Concentrated supply and team tokens without vesting

RugCheck warns when the top 10 holders own more than 50% of supply, and Jupiter's verification values a healthy distribution over a large holder count. Unlocked team tokens are an overhang the market prices in. Lock them with Jupiter Lock, free apart from network fees, with a cliff and linear unlock, and publish the wallet addresses.

#11. Choosing between Pump.fun and your own pool blindly

Fees and mechanics are from Pump.fun's program docs.

Graduation is the exception, not the rule. The Block reported a one-day graduation rate of 6.7% at the end of July 2026, about eight times June's average, after Pump.fun's BOOST started spending about 20% of migration liquidity on buy-and-burn (The Block).

#12. Ignoring DexScreener and Jupiter

DexScreener lists a token after the first transaction in a pool, but takes the logo and socials from external lists such as CoinGecko; paid Enhanced Token Info speeds this up, from $299 at the time of writing (DexScreener). Jupiter verification is free in the standard queue, while Express review costs 1,000 JUP and buys speed, not approval. Jupiter calls a project-dedicated X account with organic engagement the most important criterion and removes verification when liquidity is gone (Jupiter docs).

#Legal and safety mistakes

#13. Promising returns

In a staff statement of February 27, 2025, the SEC said that typical meme coins, bought for entertainment and speculation with no yield or rights, are not securities, though fraud remains prosecutable (SEC). The joint SEC/CFTC interpretation of March 17, 2026 adds the catch: a token becomes part of an investment contract when it is sold with promises of essential managerial efforts that buyers expect to produce profits (Jones Day summary). So do not promise returns, buybacks, "guaranteed" rewards or roadmap-driven profits.

#14. Copycat names and scam patterns

Copying a trending token's name, ticker or logo gets you flagged: Jupiter removes verification for ticker conflicts, and Phantom warns users about copycat tokens. Pump.fun's terms prohibit trademark infringement, deceptive affiliation and price manipulation. Also avoid anything that resembles a known scam pattern: an active freeze authority, a raisable transfer fee, a permanent delegate, unlocked LP, bundled supply. Scanners cannot read intentions, only the chain.

#How ChainTx.Tools helps

• Solana Token Creator. Token-2022 is preselected, mint and freeze authority are revoked by default, decimals default to 6 and supply to 1,000,000,000 (with a u64 check), and the transfer fee is 0. The logo, description and socials go into a metadata JSON pinned to IPFS. A pre-flight check blocks the launch if your balance cannot cover rent and fees, and the token is created in one transaction, rebuilt with a fresh blockhash if approval takes too long.
• Set/Update Authority tab of the same creator: revoke or transfer the mint and freeze authority of an existing token, or make Metaplex metadata immutable. Native Token-2022 metadata and fee authorities are not handled there.
• Wallet creator: fresh deployer and treasury wallets, generated locally in your browser.
• One-to-many sender: distribute team, marketing or airdrop allocations in one run.
• Market maker: automated strategies on Jupiter, Pump.fun, Raydium and Meteora pools. Use it to support liquidity, not to fake volume: Jupiter's organic score is built to filter out bot trading. See our market maker cookbook.
• Burn & claim: burns the entire balance of selected token accounts and closes them, returning about 0.002 SOL of rent each. For LP, Raydium Burn & Earn is usually better because you keep the fees.
• Bulk balance checker: check many wallets at once.

#Summary

Most failed Solana launches fail on things visible on-chain within minutes: active authorities, risky extensions, a pool with a few SOL in it, unlocked LP, bundled supply and unvested team tokens. None of them is hard to avoid. Revoke what you do not need, keep extensions minimal, size the pool to real trades, lock the LP, vest team tokens, launch without self-sniping and promise nothing beyond what the code guarantees.