| Risk factor | Finding | Evidence | Date |
|---|---|---|---|
| Sellable | Yes | Transfer simulation | 4 Sept 2026 |
| Buy tax | 0% | Contract | 4 Sept 2026 |
| Sell tax | 0% | Contract | 4 Sept 2026 |
| Admin mint | Not present | Contract | 4 Sept 2026 |
| Transfers pausable | Enabled | Contract | 4 Sept 2026 |
| Address blacklist | Enabled | Contract | 4 Sept 2026 |
| Upgradeable proxy | No | Contract | 4 Sept 2026 |
| Source verified | Yes | Block explorer | 4 Sept 2026 |
| Top-10 holders | 38.7% | Holder distribution | 4 Sept 2026 |
| Liquidity locked | No | LP holders | 4 Sept 2026 |
| Holders | 585352 | Token contract | 4 Sept 2026 |
This automated check found that PEPE's contract includes a function allowing the owner to pause transfers, meaning that at any point holders could be prevented from moving or selling their tokens if this function were activated. The contract also supports blacklisting, which would allow specific wallet addresses to be blocked from transacting, again at the owner's discretion. On the date of this check, no admin minting function was detected, meaning there is no on-chain evidence of a mechanism to create new tokens beyond the existing supply, and no upgradeable proxy was detected, meaning the contract logic cannot be silently swapped out after deployment. Buy and sell taxes were both recorded at 0%, and a transfer simulation indicated the token is currently sellable. Liquidity was found to not be locked, which means whoever controls the liquidity pool could withdraw it, and top-10 wallets were found to hold 38.7% of total supply, indicating a fairly concentrated distribution among a small number of addresses.
It's important to understand what this check does not cover. This is an automated read of the contract's code and on-chain data only — it does not assess who is behind the project, whether the team has a history of past conduct worth reviewing, how the token's economics are designed to function over time, or whether any legal or regulatory structure exists around it. A high score here reflects the absence of certain detected contract-level risk mechanisms; it says nothing about the intentions of those who control the pausable or blacklist functions, nor does it confirm the project's broader legitimacy.
Before considering any transaction, it would be worth looking into who holds administrative control over the pause and blacklist functions, and whether that control sits with a multisig wallet, a timelock, or a single private key, since this affects how easily those powers could be exercised. It's also worth checking where the liquidity currently sits, who controls that pool, and whether there is any public commitment or history regarding locking it. Reviewing the concentration of the top holders in more detail, checking transaction history for large wallet movements, and researching the project's public communications, team identity, and community discussion are all reasonable next steps before forming a view.
Contracts change after they are checked. Leave an email or a Telegram chat ID and we will tell you the moment this one does — taxes raised, minting switched on, liquidity unlocked. Free for three contracts, no account and no password.
We checked 18 points out of 100.
The other 82 are where money is usually lost: who the team is, where the tokens sit, what the documents actually say, and what the project chose not to put on its front page.