| Risk factor | Finding | Evidence | Date |
|---|---|---|---|
| Sellable | Yes | Transfer simulation | 8 Sept 2026 |
| Buy tax | No data | Contract | 8 Sept 2026 |
| Sell tax | No data | Contract | 8 Sept 2026 |
| Admin mint | Not present | Contract | 8 Sept 2026 |
| Transfers pausable | Not present | Contract | 8 Sept 2026 |
| Address blacklist | Not present | Contract | 8 Sept 2026 |
| Upgradeable proxy | Yes | Contract | 8 Sept 2026 |
| Source verified | Yes | Block explorer | 8 Sept 2026 |
| Top-10 holders | 64.1% | Holder distribution | 8 Sept 2026 |
| Liquidity locked | No | LP holders | 8 Sept 2026 |
| Holders | 21985 | Token contract | 8 Sept 2026 |
| Contract deployed | 10 Nov 2024 — 667 days ago |
| Deployment transaction | 0x1a8de6…8f96e9 |
| Deployed by | 0x937ce2…8afed5 |
| Holders | 21,985 |
| Rank | Address | Share |
|---|---|---|
| #1 | 0x9d03bb…0e5123 | 39.11% |
| #2 | 0x6abfd6…aaf6a2 | 8.99% |
| #3 | 0x53051e…79b281 | 4.21% |
| #4 | 0x3154cf…0f2c35 | 3.01% |
| #5 | 0x72b23a…696fae | 2.86% |
This automated check scored MORPHO 13 out of 18 on contract mechanics observed on Ethereum at the time of the scan. A few findings are worth translating into plain terms. The contract is deployed as an upgradeable proxy, which means the code that actually runs the token can be swapped out later by whoever controls the upgrade function — in practice, this gives that party the ability to change how the token behaves after you've bought it, including introducing mechanics that don't exist today. Separately, the top 10 wallet addresses hold 64.1% of the total supply, a concentration level that means a small number of holders could move a large share of the token's supply at once, which can affect liquidity and price if they choose to sell. On the positive side, no admin mint function, transfer-pausing mechanism, or address blacklist function was detected in the contract, and a transfer simulation indicated the token can currently be sold — no honeypot behaviour was detected on this pass. The contract source code is also verified on the block explorer, meaning the deployed code is publicly readable and matches what's shown there. Liquidity is not locked, meaning whoever supplied the trading pool can withdraw it, which is a separate risk from the token contract itself.
It's important to be clear about what this check does not cover. This is an automated read of the contract's code and on-chain data only — it does not evaluate who is behind the project, whether the team's identity or history is trustworthy, how the tokenomics are structured beyond raw holder percentages, whether any legal or regulatory structure exists, or what the team's actual intentions are. A high score here reflects an absence of certain detected contract-level red flags on the day of the check; it is not a judgment of the people or business behind the token, and findings can change if the contract is upgraded or liquidity conditions shift.
Before putting money in, it's worth digging into who holds the admin or upgrade keys for this proxy, since that address effectively controls the token's future logic — tools like the block explorer's contract page can show recent admin activity. Check whether the top holders include known exchange or treasury wallets versus unidentified individual wallets, as this changes the interpretation of concentration. Look into whether the liquidity pool has any other form of commitment (such as a long-standing, unmoved LP position) even though it isn't formally locked. Finally, look beyond this contract check entirely: research the team's public track record, read the project's own documentation on token distribution and vesting, and confirm the contract address you're checking matches the one officially published by the project, since address mix-ups are a common source of loss.
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 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.