How to read a token contract: 6 critical permissions
A token's contract decides what it can do. Even if you cannot read code, a few permissions shown by security tools reveal the biggest risks. These 6 items tell you how much power the contract gives its owner.
1. Ownership and renounce
If the contract has an owner, that owner uses the permissions below. If ownership is renounced, they can no longer be used. But with a "hidden owner" or "reclaim ownership" feature, renouncing alone guarantees nothing.
2–6. Permissions to check
- 2. Mint: the owner can increase the supply at will and sell it into the market.
- 3. Proxy (upgradeable contract): the code can be replaced entirely later; a clean contract today can be a honeypot tomorrow.
- 4. Blacklist / whitelist: specific wallets can be blocked from buying or selling.
- 5. Pause: the owner can stop all transfers.
- 6. Change tax: buy and sell taxes can be raised to 99% later.
Source code verification
Verified source code is code anyone can read on the block explorer. Nobody can see what an unverified contract does; that alone is a serious warning.
For EVM tokens, Dexpion runs its own contract test next to the GoPlus scan: it checks ownership and the proxy slot, and simulates whether the owner can block sells or mint through known functions. An unknown result is never shown as ✓.
FAQ
Is a renounced contract always safe?
No. Renouncing removes the owner's powers, but the contract may have been written as a honeypot from the start, or the LP may be unlocked.
How do these permissions look on Solana?
On Solana they appear as mint and freeze authorities. Both should be revoked; Dexpion shows this as a separate check.
