| Risk factor | Finding | Evidence | Date |
|---|---|---|---|
| Sellable | Yes | ChainSift simulation | 12 Nov 2026 |
| Buy tax | 0% | Contract | 12 Nov 2026 |
| Sell tax | 0% | Contract | 12 Nov 2026 |
| Admin mint | No data | Contract | 12 Nov 2026 |
| Transfers pausable | No data | Contract | 12 Nov 2026 |
| Address blacklist | No data | Contract | 12 Nov 2026 |
| Upgradeable proxy | No data | Contract | 12 Nov 2026 |
| Source verified | No | Block explorer | 12 Nov 2026 |
| Liquidity locked | No | LP holders | 12 Nov 2026 |
| Holders | 0 | Token contract | 12 Nov 2026 |
| Deployed by | 0xbd0dcc…500032 |
This automated check scored Max coin 0 out of 4 on Base, which reflects the limited information available rather than a confirmed clean or dangerous result. An automated sell simulation found the token could be sold at the time of testing, with a 0% buy tax and 0% sell tax reported directly from the contract. No honeypot behaviour was detected in that simulation. However, because the contract source code is not verified on the block explorer, ChainSift could only read bytecode, not readable logic, so key owner-control functions — the ability to mint new tokens, pause transfers, blacklist specific addresses, or upgrade the contract through a proxy — were not reported and could not be scored either way. This is different from confirming those functions don't exist; it means they could not be checked. Separately, the liquidity backing this token is not locked, which means whoever controls that liquidity pool retains the ability to withdraw it, potentially leaving holders with tokens that have no trading pair to sell into. The holder count was reported as zero, which itself is unusual and limits confidence in how distributed ownership currently is.
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 is behind the project, how tokens are allocated among the team and early holders, whether there is a working product or roadmap, or whether any marketing claims are accurate. A contract can look mechanically unremarkable and still be attached to a project with no real activity, concentrated holdings, or undisclosed arrangements. None of that is visible from bytecode or tax settings, and nothing here should be read as a statement about the people running this token or their intentions.
Given the unverified source and the absence of a liquidity lock, a sensible next step is to look up the contract directly on the Base block explorer and check whether the code has been verified since this scan, since verification would allow a fresh read of the actual functions rather than relying on bytecode alone. It's also worth checking the liquidity pool directly — who holds the LP tokens, and whether any portion is time-locked through a third-party locker. Reviewing the holder distribution list, when available, can show whether balances are concentrated in one or two wallets. Finally, searching the contract address and any associated team names across independent sources can surface context this type of automated check is not designed to capture.
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.