Mint and freeze authority, explained
Two fields on a mint account decide how much power the creator retains over everyone who holds the token. Both are visible in seconds, both are checked by anyone doing diligence, and leaving either enabled without explanation ends most evaluations immediately.
Two authorities, two different powers
When a token is created, the mint account records who is allowed to do certain privileged things to it. Two of those fields matter to everybody who will ever hold the token.
Mint authority controls supply. Whoever holds it can create more tokens whenever they choose.
Freeze authority controls movement. Whoever holds it can freeze individual token accounts, preventing those holders from transferring or selling.
They are independent. A token can have one, both or neither, and they are set separately. They are also entirely separate from the metadata update authority, which controls the name and symbol and nothing else. Conflating the three is common and leads to worrying about the wrong one.
What mint authority permits
Unlimited creation of new supply, at any moment, with no notice.
The practical consequence is that every supply-derived figure becomes provisional. Market capitalisation is computed from circulating supply; if supply can double tomorrow, today's valuation describes a situation that can be changed unilaterally by one party. So does every holder's percentage of the total.
This is why an active mint authority ends most evaluations within seconds. It is not that the creator will necessarily print more; it is that they can, and no amount of good intent is visible on-chain. A holder is being asked to trust a promise where a disabled field would have removed the need for one.
Legitimate reasons do exist. A project with a published emission schedule, a game with in-play issuance, a token designed to expand under stated rules. In every one of those cases the requirement is the same: say so publicly, explain the rules, and expect the question anyway.
What freeze authority permits
Preventing specific accounts from transferring. A frozen account holds its balance and can do nothing with it.
For an ordinary community token this is difficult to justify. It means the creator can, at will, stop any particular holder from selling, which is the single power holders are most concerned about and the mechanism behind a good share of tokens that turn out to be untradeable. The sell failure guide covers how to distinguish this from the far more common depth problems that produce the same symptom.
Where it does appear legitimately is in tokens with regulatory or compliance requirements, where the issuer is obliged to be able to restrict transfers. That is a real category and it is not what most Solana tokens are. If your token is not in it, the field should be disabled, and if it is, that should be stated prominently rather than discovered.
There is a third power worth mentioning because it produces the same category of concern through a different mechanism. Newer token standards allow behaviour to be attached to transfers themselves, including hooks that run whenever tokens move. Legitimate applications exist, and so does the version where such a hook restricts who may transfer and under what conditions. A token using extensions therefore needs the same question asked of it as one with a live freeze authority, and the answer is less visible because it lives in program logic rather than in a field on a page.
Checking both in seconds
- Copy the mint address, not the ticker. Symbols are duplicated constantly.
- Open it in any Solana explorer. The account page displays both fields.
- Read what each says. Either an address, meaning the authority is live and held by that address, or an indication that it has been disabled.
- Check the update authority too while you are there, since it decides whether the name and symbol can change.
- If any is live, look for an explanation from the project. Its absence is itself information.
The whole check takes under a minute and it is the highest-value minute available in evaluating any token. The on-chain reading guide covers the rest of the same screen, including the fields that are frequently misread as alarming when they are not.
When keeping one is defensible
| Situation | Authority | Defensible? |
|---|---|---|
| Published emission schedule | Mint | Yes, if the rules are public |
| Game or app with in-play issuance | Mint | Yes, if explained |
| Regulated or compliance-bound issuance | Freeze | Yes, and expected |
| Ordinary community token | Either | No |
| "We might need it later" | Either | No, and it reads badly |
The bottom row is the common case and it deserves being blunt about. Retaining an authority because it might be useful is asking every holder to accept an open-ended risk in exchange for your convenience. If there is no concrete plan that requires it, the honest choice is to disable it.
One further nuance about the middle rows. An authority held by a multi-signature arrangement is materially different from the same authority sitting on a single wallet, and buyers who know what they are looking at will treat it differently. If a token genuinely needs a live mint authority for a stated emission schedule, moving that authority somewhere that requires several parties to act removes most of the concern without removing the capability. It is more work than disabling and less work than explaining a unilateral power every time somebody asks.
Disabling, and what it means
Disabling sets the authority to none, permanently. There is no mechanism to restore it, which is precisely what makes the signal credible: the creator has given something up in a way that cannot be quietly reversed.
Two practical notes. Do it deliberately rather than as a reflex, because anything the authority enabled becomes impossible afterwards, and teams occasionally disable a mint authority before completing an allocation they still needed to issue. And publish the transaction, because the claim and the evidence are different things and anyone doing diligence will look for the second.
It is also worth understanding what disabling does not do. It does not lock liquidity, which is a separate action with separate consequences. It does not stop insiders selling tokens they already hold. It does not make the token safe in any general sense; it removes two specific powers and leaves everything else exactly as it was.
That narrowness is the point. These fields are not a verdict on a project, they are a floor. Failing them ends the conversation immediately; passing them means the conversation can begin, which is why the launch checklist puts them among the first items rather than treating them as an optional polish step.
Frequently asked questions
01What does mint authority do?
It allows whoever holds it to create new tokens of that mint at any time. While it exists, the supply figure you see is the supply today rather than the maximum, which changes what a holding is worth in a way no chart reflects.
02What does freeze authority do?
It allows the holder to freeze individual token accounts. A frozen account cannot transfer, which means the holder cannot sell. For an ordinary community token there is essentially no legitimate need for this, and its presence is behind many reports of tokens that cannot be sold.
03How do I check them?
Open the mint address in any Solana explorer. Both fields are displayed on the account page, showing either an address or that the authority has been disabled. It takes about five seconds and it is the first thing experienced buyers look at.
04Is it always bad to keep an authority enabled?
Not always, but it always requires an explanation. Some tokens have genuine reasons, such as a planned emission schedule or a regulated use case that requires freezing. What is fatal is retaining one without saying so, because the discovery then happens without your framing attached.
05Can authorities be re-enabled after being disabled?
No. Disabling is permanent and irreversible, which is exactly what makes it a credible signal. It is also why the decision should be made deliberately rather than as a reflex, since anything the authority was needed for becomes impossible afterwards.
06Do these affect a volume campaign?
Not mechanically, since routing swaps does not touch either authority. They affect everything downstream of a campaign, because visitors arriving from any activity check them within seconds and a live authority ends the evaluation before the chart matters.
Keep reading
The free checks come first
A campaign brings people to look. Two fields decide what they conclude in the first five seconds.
Open the volume console