| Risk factor | Finding | Evidence | Date |
|---|---|---|---|
| Sellable | Yes | ChainSift simulation | 22 Nov 2026 |
| Buy tax | 0% | Contract | 22 Nov 2026 |
| Sell tax | 0% | Contract | 22 Nov 2026 |
| Admin mint | Enabled | Contract bytecode | 22 Nov 2026 |
| Transfers pausable | No data | Contract | 22 Nov 2026 |
| Address blacklist | No data | Contract | 22 Nov 2026 |
| Upgradeable proxy | No data | Contract | 22 Nov 2026 |
| Source verified | No | Block explorer | 22 Nov 2026 |
| Liquidity locked | No | LP holders | 22 Nov 2026 |
| Deployed by | 0x4e59b4…b4956c |
This automated check scored PZCCM 0 out of 4 on the indicators it looks at, and it is worth understanding exactly what that means. The contract's bytecode shows that an admin mint function is enabled, which means whoever controls the contract can create new tokens at will. In practice, this lets the owner increase the total supply at any time, which can dilute the value of tokens already held by others. The contract's source code is not verified on the block explorer, meaning the human-readable code behind it has not been published or confirmed to match what's deployed — this limits what can be checked at all, since the review has to rely on reading raw bytecode rather than clear source. Liquidity is also not locked, which means whoever supplied the trading pool can withdraw it from the exchange at any point, potentially leaving holders unable to sell at a meaningful price even if the contract itself permits selling. On the positive side, no honeypot behaviour was detected — the simulation found the token sellable at the time of the check, with 0% buy and sell tax recorded in the contract. Several other mechanics, including whether transfers can be paused, whether addresses can be blacklisted, and whether the contract sits behind an upgradeable proxy, returned no data from the source used and were not scored either way.
It's important to be clear about what this check does not cover. This is an automated read of contract mechanics only — it does not assess who the team behind PZCCM is, whether their stated plans or tokenomics are realistic, whether any legal entity stands behind the project, or what their intentions are. A low score reflects technical permissions built into the contract, not a judgement about the people running it or the likelihood of the project succeeding or failing.
Given the unverified source, enabled mint function, and unlocked liquidity, anyone considering this token would reasonably want to look further before deciding anything. That could include searching for the project's own communications about who holds the owner/admin keys and why, checking whether the liquidity pool address is publicly known and monitoring it independently, looking at the distribution of token holders to see how concentrated ownership is, and watching whether the team has published or plans to publish verified source code. None of this guarantees an outcome either way — it simply gives a fuller picture than contract mechanics alone can provide.
Contracts change after they are checked. Tell us where to reach you and we will say when this one does. Free for three contracts, no account.
We checked 4 points out of 100.
A deep check also reviews the project's public materials, team, tokenomics and disclosures.