How to Launch a Token on Solana That Isn't a Memecoin

Almost every "how to launch a token on Solana" guide, including several on this site, is really a memecoin guide. It tells you 1 billion supply, 6 decimals, revoke everything, seed a pool, burn the LP. That advice is tuned for an asset whose realistic lifespan is measured in hours, where the only job of the config is to prove within thirty seconds on Solscan that the deployer cannot rug you. If you are launching a game currency, a governance token, a loyalty point, or a creator coin, at least two of those five defaults will hurt you — and one of them, revoking mint authority, is unfixable.

Quick Facts

The mint transaction is identical in both columns. The SPL Token Program does not know or care what your token represents; it exposes the same three authority fields and the same immutable decimals to a meme and to a central bank. Everything in the right-hand column is a policy choice you are making on top of neutral infrastructure.

The memecoin default is a survival heuristic, not a standard

The reason memecoin guides say "revoke everything" is sound in context. A trader has maybe thirty seconds to decide on an unknown token, and the only cheap signals available are on-chain: is mintAuthority null, is freezeAuthority null, is the LP burned. Against that audience, a live mint authority reads as "the deployer can print more and dump," and the token is filtered out before anyone reads the pitch. In our own launch-survival work, revoked mint authority correlates with a 4.2× higher 24-hour survival rate — the detail is in why most Solana memecoins die in 24 hours.

That heuristic answers a specific question: how do I get an anonymous stranger to buy in the next five minutes? If your token is issued to a community that already knows who you are, redeemed inside a product you operate, or voted with in a DAO whose treasury is public, that is not the question you are answering. You are answering a slower one: will this still work when the program has ten times as many users?

The honest version of the advice is that revoking mint authority buys trust from strangers at the cost of every future issuance. For a meme, there are no future issuances, so the trade is free. For a game token, the future issuances are the product.

What fourteen live Solana tokens actually do

Rather than argue this from principle, here is the on-chain state of fourteen mints, read directly from Solana mainnet via the getAccountInfo RPC method on 2026-08-11. You can reproduce any row in one call — the mint account exposes decimals, supply, and both authority fields with no interpretation needed.

Supply is the mint's total on-chain supply, not circulating supply — treasury, vesting contracts and unclaimed rewards are all included. Authority state is a point-in-time snapshot; a project can revoke tomorrow, which is exactly the migration path argued for below.

Mints with a LIVE mint authority, by category
(14 Solana mints, read from mainnet 2026-08-11)

Memecoin          n=2  ················  0/2   BONK, WIF
Governance        n=3  ················  0/3   JTO, PYTH, W
DEX token         n=3  ▓▓▓▓▓···········  1/3   RAY, JUP, ORCA
Gaming            n=2  ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓  2/2   ATLAS, POLIS
DePIN / protocol  n=3  ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓  3/3   HNT, RENDER, MPLX
Stablecoin        n=1  ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓  1/1   USDC

Two readings matter here. The first is that a live mint authority is not a scam signal — RENDER and USDC are among the most scrutinised assets on the network and both keep mint and freeze authority active. The second is subtler: the tokens that revoked are overwhelmingly the ones whose distribution was already complete at launch. JUP, PYTH, W and JTO all minted their supply at genesis and moved it out through airdrops and vesting contracts rather than through ongoing issuance — which is exactly what a null mint authority alongside a nine-or-ten-figure supply tells you. Revocation there was not a trust gesture bolted on; it was an accurate description of a supply schedule with nothing left to run.

That is the actual rule. Revoke when your supply is genuinely final. Keep it, behind a multisig, when it is not. Doing the reverse in either direction is the mistake.

Decision 1: mint authority, and the multisig middle path

The binary framing — revoke or don't — hides the option most serious projects take, which is to move the authority somewhere a single compromised key cannot use it. On Solana that generally means Squads, the standard multisig for program and token authority management, whose documentation covers transferring an SPL mint authority to a multisig vault.

Mint authority: the decision, in order

Is every token that will ever exist already minted?
 │
 ├─ YES ─► REVOKE NOW.
 │         Costs you nothing, buys the strongest
 │         cheap trust signal on the network.
 │
 └─ NO ──► Is the remaining issuance on a published schedule?
            │
            ├─ NO ──► DO NOT LAUNCH YET.
            │         An undisclosed, uncapped mint authority
            │         is the thing holders are right to fear.
            │
            └─ YES ─► TRANSFER TO A MULTISIG.
                      Publish the signer set and the schedule.
                       │
                       ▼
                      Schedule finished? ── no ──► keep emitting
                       │                              │
                      yes                             │
                       │                              │
                       ▼                              │
                      REVOKE. ◄─────────────────────── ┘
                      The multisig has done its job.

The sequence matters. Transferring authority to a multisig and revoking are separate transactions against your own mint, and neither has to happen on launch day — the mechanics are in transfer mint authority on Solana and how to revoke mint authority, and the standalone action lives at revoke mint authority whenever you are ready. What you cannot do is un-revoke. There is no recovery path, no governance override, no support ticket. The mint account field is set to None in the account state and the program will refuse every future mint instruction forever.

Freeze authority is a different conversation and a shorter one. It lets the issuer freeze any holder's token account, which is a compliance tool for regulated issuers and a liability for everyone else. Twelve of the fourteen mints above have revoked it; the two that have not are a stablecoin and a DePIN network with real-world legal exposure. Unless you are in that category, revoke it — and note that the create flow on this site revokes freeze authority unconditionally, so the decision is made for you.

Decision 2: decimals and supply, one permanent and one not

Decimals are set when the mint account is created and are immutable for the life of the token. There is no upgrade path, no migration short of launching a new mint and asking every holder to swap. This is the single most permanent choice on the list, and the census above shows there is no universal answer:

The test to apply: what is the smallest amount a user should ever be able to hold, and does your decimal count let them hold it? A loyalty program that ships at 6 decimals will spend years explaining why a balance reads 100.000000.

Supply is the opposite — it feels permanent and is not, provided mint authority survives. The memecoin instinct is to pre-mint the lifetime maximum because there will be no second chance. A game economy that pre-mints ten years of rewards has instead created a ten-year overhang sitting in a treasury wallet that every prospective holder can see and price in. Mint what year one needs, keep the authority behind the multisig, and issue the rest visibly. ATLAS runs exactly this shape. Minting additional supply later is a routine operation via mint tokens on Solana.

Keep update authority, too. It controls the Metaplex Token Metadata account holding your name, symbol and image URI. Memecoins revoke it to signal that the branding can never be swapped for something else after listing. A project that may rebrand, fix a broken image host, or move its metadata JSON will want it — the full editable-versus-immutable breakdown is in can you edit a Solana token after launch, and update metadata is the tool for it.

Decision 3: distribution, which is the actual work

A memecoin launch has no distribution phase. Supply goes into a pool, the market distributes it, and the deployer's job is to be visible for four hours. Every other kind of token has to answer where the supply goes and when — and this is where most non-memecoin launches actually fail, long after the mint transaction confirmed cleanly.

Name your buckets publicly before launch. The percentages below are a shape, not a benchmark; publish your own and then honour them.

An undisclosed team allocation is the single fastest way to lose a community that would otherwise have been forgiving. A team allocation that is disclosed, cliffed and visibly vesting on-chain is close to a non-issue. The difference is not the size of the number; it is whether holders found it in your docs or on Solscan.

Vesting needs a program, not a promise. Streamflow is the common Solana choice for token vesting and streaming payments, and for DAO governance and treasury control Realms is the reference implementation on top of SPL Governance — you can browse live DAOs at app.realms.today. For one-off community distributions, batch sending is covered in how to airdrop Solana tokens, with the tool at airdrop tokens.

Pre-launch checklist for a token that has to outlive launch week.

1. ☐ Decimals justified in writing, against the smallest unit a user should hold — it is immutable after the mint transaction
2. ☐ Supply sized to year one, not to the lifetime maximum, unless issuance is genuinely finished
3. ☐ Mint authority destination decided: revoke now, or multisig with the signer set published before launch
4. ☐ Allocation table published with every bucket named, including the team's
5. ☐ Vesting deployed on-chain before any allocation is announced, not promised in a blog post
6. ☐ Liquidity plan chosen: no pool, locked LP, or burned LP — and the reason written down
7. ☐ Update authority retained unless the branding is genuinely final

Decision 4: liquidity for a token that is not meant to spike

Three viable answers here, and the memecoin one is usually the worst fit.

No pool at all. A loyalty point or internal game currency that redeems against your product does not need a market price. A mint with no pool still transfers, still shows in Phantom once metadata is attached, and simply has no chart. Opening a thin pool for a token nobody was going to trade creates a price that makes your product look broken every time it moves 40% on a 2 SOL order.

A pool with locked LP. The default for a project that intends to manage liquidity for years. You keep the ability to migrate venues, widen the range, or add depth as volume grows, and you publish an unlock schedule so holders can verify you have not quietly pulled it. Pool creation on Raydium is documented in their CPMM flow and walked through in how to add liquidity to Raydium; the tool is at create liquidity.

A pool with burned LP. Maximum trust, zero flexibility, permanent. Correct for a memecoin, rarely correct for a treasury that will still exist in three years. The mechanics and the proof-sharing convention are in how to burn LP tokens and LP burn proof, with the tool at burn liquidity. Treat it as a one-way door and be sure before you sign.

Fee tier follows from the same logic. The 1% tier that memecoins use is priced for volatile, high-churn speculation. A governance or utility token trading in a stable range is better served by 0.25%, which is what ORCA, JTO and the rest of the DeFi cohort sit behind, and cheap swaps matter more than fee extraction when you want the token to be usable.

The launch sequence, in order

Launch sequence for a token that has to work in year three

 WEEK -6 to -3   allocation table written, emission schedule
                 capped, multisig signers named publicly
 WEEK -3 to -1   vesting program deployed on-chain, docs published
 ══════════════════════════════════════════════════════════════
 LAUNCH DAY      mint · decimals set forever · freeze revoked
 (~1 second)     mint authority ──► multisig
 ══════════════════════════════════════════════════════════════
                 Does this token need a public market?
                  │
                  ├─ NO ──► distribute to holders. Stop here.
                  │         No pool, no chart, no price.
                  │
                  └─ YES ─► open pool · lock LP · publish the
                            unlock date · submit to aggregators
 MONTH 1+        emit on schedule, from the multisig, in public
 SUPPLY FINAL    revoke mint authority · announce that you did

The mint costs the same as a memecoin's, because it is the same transaction — roughly 0.22 SOL all-in through a no-code creator, of which about 0.0191 SOL is the unavoidable protocol floor for mint rent, metadata rent and network fees, itemised in cost to create a Solana token. Nothing about that number scales with how serious the token is. What scales is the preparation on either side of it, and that is where a launch built to last actually differs from a meme.

After launch, the visibility steps are the same for every token type: aggregators index a new pool within minutes, and the Jupiter listing process, DexScreener token info, and wallet rendering are covered in how to verify a Solana token.

Where this tool stops fitting

Stating the limits is more useful than pretending there are none:

• Freeze authority is always revoked in this create flow and cannot be kept. A regulated issuer that needs a live freeze authority — the USDC and RENDER pattern — needs a different deployment path, most likely the CLI plus a Metaplex metadata call.
• No vesting, no multisig setup. The mint is created; Squads and Streamflow are separate deployments you do yourself.
• Classic SPL only, not Token-2022. Transfer fees, interest-bearing balances and confidential transfers all require the newer program — see SPL Token vs Token-2022 to decide if you need it, and note the token program repository if you are deploying it yourself.
• Mint authority is opt-out, not configurable. The form lets you keep it; it does not transfer it to a multisig for you. That is a second transaction.

Limitations

• The authority census is a 14-mint snapshot, not a survey. These were chosen as recognisable examples across categories, read on 2026-08-11. It is not a random sample and the percentages should not be read as population statistics. Every row is re-checkable in one RPC call, which is the point.
• Authority state changes. Any of these projects can revoke, or transfer, after publication. Verify before citing.
• No legal or securities analysis. Whether your token is a security in your jurisdiction is a question for a lawyer, and the answer materially affects allocation, vesting and marketing. Nothing here is legal advice.
• Distribution mechanics are summarised, not taught. Deploying Realms, configuring Streamflow schedules and designing emission curves are each their own project.
• Memecoin launches are out of scope. If that is what you are launching, the right guide is the Solana memecoin launch checklist, and the right defaults are the ones this article argues against.

References

1. SPL Token Program documentation — mint accounts, the three authority fields, decimals immutability
2. Solana docs: token basics — mint account structure and supply mechanics
3. Solana docs: account model — how authority fields are stored and nulled
4. Metaplex Token Metadata — name, symbol, URI, and update authority
5. Metaplex documentation — metadata deployment paths outside a hosted creator
6. Squads and Squads documentation — Solana multisig for holding mint authority
7. Streamflow documentation — on-chain token vesting and streaming
8. Realms documentation and live DAOs on Realms — SPL Governance in practice
9. Raydium CPMM pool creation — pool costs and fee tiers
10. Jupiter Station — aggregator listing requirements
11. DexScreener Solana — new-pair indexing
12. Phantom: Solana tokens — wallet rendering of SPL metadata
13. solana-program/token — the token program source, including Token-2022
14. Mint states read from Solana mainnet via getAccountInfo (jsonParsed) on 2026-08-11; individual mints viewable on Solscan

FAQ

Do I have to revoke mint authority when I launch a token on Solana?

No. Revoking is a memecoin convention, not a network rule. Reading 14 live Solana mints from mainnet on 2026-08-11, both memecoins in the sample had mint authority revoked — but 7 of the 12 non-memecoin tokens kept it live, including RENDER, HNT, ATLAS, ORCA, MPLX and USDC. If your token has scheduled emissions, player rewards, or a second tranche still to issue, revoking at launch permanently breaks it. Move the authority to a multisig instead and revoke later, once supply is final.

What decimals should a non-memecoin Solana token use?

It depends on the smallest unit a user should be able to hold. 6 decimals is the DeFi and governance default (JUP, PYTH, W, RAY, ORCA all use 6). DePIN and game tokens usually run 8 (RENDER, HNT, ATLAS, POLIS) because reward payouts are tiny fractions. Loyalty points should use 0 so nobody can earn half a point. Decimals are fixed at mint creation and can never be changed, so this is the one field worth an extra hour of thought.

Can I launch a Solana token without a liquidity pool?

Yes, and for a loyalty, membership or internal reward token you often should. A mint with no pool has no market price and no DEX chart — holders can receive and transfer it, but nobody can trade it. That is the correct design for points that redeem against a product rather than trade against SOL. You can always open a pool later; you cannot un-open one and reclaim the price discovery that happened in it.

Should a governance or utility token burn its LP tokens?

Usually not. LP burning is a memecoin trust signal that proves the deployer cannot pull liquidity, and it costs you the ability to migrate, rebalance, or widen the pool later. A treasury that intends to manage liquidity for years is better served by locking LP with a published unlock schedule, or by holding it in a multisig whose signers are named. Burn is permanent; a disclosed lock buys most of the same trust and keeps the option open.

How much does it cost to launch a non-memecoin token on Solana?

The mint itself costs the same regardless of what the token is for — roughly 0.22 SOL all-in through a no-code creator, of which about 0.0191 SOL is the unavoidable protocol floor for mint rent, Metaplex metadata rent and network fees. What differs is everything after: a token that never opens a pool skips the ~0.4 SOL pool cost and the seed liquidity entirely, while a governance token that wants a deep, stable market needs far more seed capital than a memecoin does.

Which token type should I pick on the create form?

Match it to what the token does, not to what you hope it trades like. Game currencies keep mint authority for rewards; governance tokens size supply for readable voting math; loyalty programs use 0 decimals; creator coins run a smaller supply so per-token prices stay meaningful to fans. If it genuinely is a meme, the memecoin template is the right one and this whole guide does not apply to you.