What a mint function is, who is allowed to call it, and why renouncing ownership doesn't always close the door.
Minting is the creation of new tokens out of nothing. A contract that can mint has a function which increases the total supply and credits the new tokens to an address — usually one the caller chooses. No trade happens, no one sells anything to anyone. The supply is simply larger than it was a block earlier.
What that does to a holder is arithmetic, not opinion. If you hold one token out of a million and the supply doubles, you now hold one out of two million. Your balance is unchanged and your share of the whole has halved, without you doing anything.
The mint function sits in the token's own contract. Next to it there is almost always a restriction saying who is allowed to run it — most often a modifier that permits only the owner, a single address recorded inside the contract.
So there are two separate facts, and they are worth keeping apart:
An automated check reads both from the deployed code. It does not need the team's cooperation and does not depend on what the documentation says.
"Ownership renounced" means the owner address was set to an address nobody controls, usually the zero address. After that, every function guarded by the owner-only restriction can never be called again, by anyone. If minting was one of those functions, minting is over.
Two things it does not do. It does not remove the function from the code — the function is still there, permanently unreachable. And it closes only what was owner-guarded: a contract can have several roles, and renouncing one of them leaves the others exactly as they were.
Renouncement is also one-way. There is no undo, which is why some projects deliberately keep ownership: to fix bugs, to adjust parameters, to run a treasury their holders voted for. Keeping it is not evidence of anything by itself.
A contract can be deployed behind an upgradeable proxy. The address people trade against stays the same, while the code it runs can be replaced later by whoever holds the upgrade rights.
This matters here because it sits above the previous question. A token with no mint function today, whose ownership has been renounced, can still gain one tomorrow if the logic behind the proxy is swapped — and the address in your wallet will not change when that happens. Renouncing ownership of the token contract and controlling the proxy admin are different things.
Whether a contract is a proxy is readable from the chain, and our free check reports it as a separate line for exactly this reason.
It reads capability, not intent. "Owner can mint new tokens" means the mechanism exists and someone can reach it. It does not say they will, and a project with mint rights and a public reason for holding them is a different situation from one that never mentions them — but the contract cannot tell those two apart, and neither can we from the code alone.
That is the line we hold: the check shows you what is possible. What to make of it depends on who holds the key, what they have said they will use it for, and whether that holds up — questions the chain does not answer.
All four come out of the same free check. Paste a contract address — it reads the live contract and shows the date it read it.