HostLaunch a Solana Token with a Revoked Mint Authority
The first thing a buyer's scanner checks on a new Solana token is whether the mint authority is null. Here is how to actually do it — the order that matters, the tools that do it for you, and the three flags a revoked mint does not settle.
When a Solana token launches with its mint authority set to null, the deployer has given up the power to ever create new tokens again. The supply minted at launch is the supply forever. That one field is what scanners flag as "mint revoked" or "renounced," and it is the first thing experienced buyers look at — because a live mint authority means the deployer can print a billion tokens tomorrow and sell them into the liquidity pool, diluting every holder toward zero. If you are launching a token, getting this right is not optional. It is the difference between a launch buyers will touch and one they will not.
What a null mint authority actually proves
Every SPL token has a mint account, and one field on it — the mint authority — names whoever can sign a MintTo instruction. While that field holds an address, that address can create new tokens at will, in any amount, to any account. When it is set to none, no signature exists that can mint again. The change is permanent: there is no holder left to reassign the power, and the protocol offers no recovery path.
That permanence is what makes the signal valuable. A revoked mint cannot be faked at the protocol level — either the field is null or it is not, and a buyer can verify it on-chain in a second without trusting you at all. It is the single strongest statement a launch can make, precisely because it is impossible to take back.
The order that matters: mint → distribute → revoke
The sequence is where launches go wrong. Revoke too early and you lock yourself out of minting the rest of your intended supply — a launch that promised 40% to a presale can only ever mint what it already has. Revoke too late — after the liquidity pool is live — and the first buyers watched an active authority the whole time. Neither is recoverable.
The order that holds up:
- Create the mint with yourself as mint authority.
- Mint the entire intended supply in one pass — every token that will ever exist.
- Allocate it: move the LP-side amount to the pool wallet, the team allocation to its wallets, any airdrop or presale commitments to theirs.
- Revoke the mint authority — set it to none — before liquidity opens.
- Then handle the rest of the trust stack: freeze authority, LP tokens, metadata — covered below.
Launchpads collapse this into one transaction flow. On pump.fun-style platforms the mint authority is revoked automatically at creation — you never hold it, which is why buyers treat pump.fun graduations as baseline-clean on this flag. If you are launching manually, the revocation is one instruction:
spl-token CLI: spl-token authorize <MINT_ADDRESS> mint --disable — signed by the current mint authority. Run it, then verify on an explorer that the mint authority reads null before you announce the pool.
Revoked mint is step one of four
A null mint authority fixes supply inflation — and only that. Scanners print it first because it is crisp, not because it is sufficient. The other flags a buyer's tool checks on the same page:
| Check | What it asks | Done right |
|---|---|---|
| Mint authority | Can new supply be printed? | Null — revoked before liquidity |
| Freeze authority | Can a holder's account be frozen? | Revoked too — it is a separate field with its own SetAuthority |
| LP tokens | Can the pool be pulled? | Burned outright, or locked in a known locker for a real term |
| Distribution | Who already holds the supply? | No dev-side cluster that can dump — see reading holder distribution |
A revoked mint with a live freeze authority is half a promise — the token cannot inflate, but any holder's account can still be frozen at the authority's discretion. A revoked mint where the deployer kept 60% of supply is worse: supply is fixed, and most of it is in one wallet. And none of the authority flags say anything about the LP tokens themselves — whoever holds them can still withdraw the pool. Buyers' scanners read all of it at once, and the launches that earn "clean" marks clear every row, not just the top one.
Why buyers weight this flag so heavily
Because supply inflation is the cheapest rug to run and the most absolute when it lands. An unlocked pool gets pulled in one transaction, but a live mint authority is a standing option — the deployer can wait weeks for liquidity to deepen, mint an enormous batch, and drain the real money out at the top. Jupiter's verification process, DEX scanners, and wallet warnings all key on it for the same reason: it is the one risk a deployer can eliminate provably, at zero cost, before asking anyone for money. Declining to is itself a signal.
The one-line rule for creators: revoke the mint before liquidity, revoke the freeze while you are there, and deal with the LP in the same launch transaction flow. A "mint revoked" flag surrounded by live flags does not make a token look safe — it makes the missing revocations look deliberate.
Token-2022: where "revoked mint" is not the whole read
On the newer Token-2022 program, a null mint authority is necessary but no longer sufficient, because extensions can reintroduce issuer powers the old program never had. A permanent delegate extension can transfer or burn tokens out of any holder's account regardless of mint status. Transfer hooks can run arbitrary logic on every move — the mechanism behind transfer taxes and soft honeypots. A metadata pointer can leave the token's name and image mutable after launch. None of these are inherently malicious — transfer hooks power legitimate fee models — but a thorough scan reads them alongside the authority flags, and a creator should know a buyer's tool will.
See your token the way buyers do
Authorities, holders, liquidity — read together, the same checks their scanners run.
Frequently asked
What does a null mint authority mean on a Solana token?
The mint account's mint-authority field is set to none — no wallet or program can ever create new tokens again. The supply printed at launch is the supply forever, and buyers read it as proof the deployer cannot inflate after they buy.
When should I revoke the mint authority during a launch?
After the full intended supply is minted and allocated, and before or at the moment liquidity goes live. Too early locks you out of minting the rest of your supply; too late means early buyers watched an active authority and priced you accordingly.
Does a revoked mint authority make my token look safe on its own?
No — it is the first line scanners check, not the only one. A live freeze authority, concentrated dev wallets, unhandled LP tokens and mutable metadata each print as separate flags. The credible launch clears all of them, not just mint.
How do I revoke mint authority on a token I already created?
Sign a SetAuthority instruction setting the mint authority to none — spl-token authorize <MINT> mint --disable on the CLI, or your token tool's revoke toggle. Most launchpads, including pump.fun-style platforms, revoke it automatically at creation.
Is "revoked" the same as "renounced" for mint authority?
Yes. Both describe the identical on-chain state — the mint authority field set to none via SetAuthority. Explorers, scanners and launchpads just use different words for it.