How to revoke mint authority with Phantom (2026)

Revoking the mint authority is the single most important trust signal you can give holders. It's irreversible: once it's done, no one — including you — can ever mint another token on that contract. This guide shows you exactly how to do it from Phantom in under a minute.

What "mint authority" actually is

Every SPL token mint has an optional mint_authority field. The pubkey stored there is the only address allowed to call MintTo. Set it to None and the supply becomes provably fixed forever. Solscan and Birdeye both surface this field in their UI — a token with Mint Authority: NULL is what holders look for.

The fastest path: bake the revoke into your launch

If you're still pre-launch, the cleanest option is to revoke inside the same transaction that creates the token. On SolanaForge's create page, flip the Revoke mint authority toggle before signing. The SetAuthority instruction is appended to the mint tx so the entire flow — create mint, mint supply, revoke — settles atomically. One signature, one fee, no race window where you could secretly mint more.

Already launched? Here's the manual flow

1. Open Phantom and confirm you're connected to Mainnet Beta.
2. Go to your token's page on Solscan and copy the mint address.
3. Use a tool that exposes spl-token authorize <MINT> mint --disable — SolanaForge ships this on the SPL Token Creator dashboard under "Manage existing token", or you can run it from the Solana CLI if you're a developer.
4. Phantom pops a single signature request. The fee is ~5,000 lamports (well under $0.01).
5. After confirmation, refresh Solscan. The "Mint Authority" row should now read NULL with a green check.

What changes after revocation

| Before | After | |---|---| | You can mint more supply at any time | Supply is permanently frozen | | Solscan shows your wallet as Mint Authority | Shows NULL | | RugCheck flags as "mintable" | Flags as "good" on this axis | | Aggregators may show a yellow warning | Warning clears |

What does not change: freeze authority, update authority, your LP position, holder balances. Those are separate fields — see Revoke mint authority explained for the full taxonomy.

Common mistakes

• Revoking on devnet by accident. Always check the network indicator in Phantom's top-right. Devnet revokes don't affect your mainnet token.
• Revoking before you've minted enough. Once mint authority is gone, you cannot add to supply for an airdrop, team allocation, or CEX listing. Mint your full intended supply first.
• Confusing mint authority with freeze authority. Two different fields. Revoking one does not revoke the other.

Bottom line

If you're launching a memecoin or any community token, revoke mint authority in the same transaction as creation. If you've already launched without it, do it before your first major marketing push — holders and aggregators check this field within seconds of seeing your ticker. Launch with auto-revoke →.