| Risk factor | Finding | Evidence | Date |
|---|---|---|---|
| Sellable | No data | Transfer simulation | 5 Nov 2026 |
| Buy tax | No data | Contract | 5 Nov 2026 |
| Sell tax | No data | Contract | 5 Nov 2026 |
| Admin mint | No data | Contract | 5 Nov 2026 |
| Transfers pausable | No data | Contract | 5 Nov 2026 |
| Address blacklist | No data | Contract | 5 Nov 2026 |
| Upgradeable proxy | No data | Contract | 5 Nov 2026 |
| Source verified | No | Block explorer | 5 Nov 2026 |
This automated check was unable to score this contract in any meaningful way, and that itself is the most important finding. The source code behind this token has not been verified on the block explorer, which means the underlying logic exists only as compiled bytecode — unreadable to this automated scanner and unreadable to you. Because of this, none of the usual checks could be completed: whether the token can be sold at all, whether a buy or sell tax is hidden in the code, whether the owner can mint new tokens at will, pause transfers, blacklist specific wallets, or swap in new logic through an upgradeable proxy. Every one of these is listed as "no data" not because the contract was checked and found clean, but because it could not be read. A clean-looking scorecard here would normally mean these behaviours were tested and not found; this is different — it means they were never tested at all.
It's worth being clear about what even a fully scored result would and wouldn't tell you. This type of check only looks at contract mechanics: the technical permissions and functions baked into the code. It says nothing about who is behind the project, whether the team has a history of similar launches, how the tokenomics are structured, where liquidity sits, whether there is a legal entity behind it, or what the stated intentions are. Mechanics and intent are separate things, and this page only ever speaks to the former — and in this case, couldn't even do that.
Given unverified bytecode and a zero-data result, there is substantially less to go on here than with a typical contract. Before considering any further action, it would be worth checking whether the contract has been verified on Etherscan since this scan was run, since verification status can change. Looking at the liquidity pool directly — its size, whether it's locked, and for how long — can offer independent signal. Checking holder distribution for concentration in a small number of wallets, reviewing the deployer wallet's history for other tokens it has created, and searching independently for any community discussion or warnings about this specific address are all reasonable next steps. Because sellability itself could not be confirmed here, treat the inability to verify this as a standalone piece of information rather than something to test by putting funds in.
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.
The other 96 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.
Trading a meme coin? The meme coin check shows how much real money is in the pool and what you lose selling $1,000, who can pull that money out, who holds the supply and how it trades — ready within 3 minutes of payment, day or night.