Free above: contract permissions, sell test and tax when data is available.
Paid report: pool balances, trading activity, large holders and estimated price impact for supported pools.
| Risk factor | Finding | Evidence | Date |
|---|---|---|---|
| Sellable | Yes | ChainSift simulation | 19 Nov 2026 |
| Buy tax | 0% | Contract | 19 Nov 2026 |
| Sell tax | 0% | Contract | 19 Nov 2026 |
| Admin mint | No data | Contract | 19 Nov 2026 |
| Transfers pausable | No data | Contract | 19 Nov 2026 |
| Address blacklist | No data | Contract | 19 Nov 2026 |
| Upgradeable proxy | No data | Contract | 19 Nov 2026 |
| Source verified | No | Block explorer | 19 Nov 2026 |
| Top-10 holders | 88.7% | Holder distribution | 19 Nov 2026 |
| Liquidity locked | No | LP holders | 19 Nov 2026 |
| Holders | 1736 | Token contract | 19 Nov 2026 |
| Deployed by | 0x2ded10…fb528c |
| Holders | 1,736 |
| Rank | Address | Share |
|---|---|---|
| #1 | 0xfd92f4…2a7eda | 13.77% |
| #2 | 0xbaed38…e9439f | 13.26% |
| #3 | 0x3304e2…7b566a | 13.13% |
| #4 | 0x1985ea…b25c87 | 12.71% |
| #5 | 0x0d0707…b492fe | 12.70% |
This automated check gave OMN (OmniousAI) a score of 1 out of 10 on Base, and it's worth walking through what that actually reflects. A simulated sell went through on the date of the check, and the buy and sell tax both read as 0%, so no honeypot behaviour or trading tax was detected at that time. However, the contract's source code is not verified on the block explorer, which means ChainSift could only read the raw bytecode rather than human-readable code. In practice, this means the usual checks for things like admin minting powers, the ability to pause transfers, blacklisting specific addresses, or an upgradeable proxy structure could not be confirmed one way or the other — they show as "no data," not as "safe." An unverified contract can contain functions that let the owner change how the token behaves after you've bought it, and nobody outside the deployer can currently see whether those functions exist. On top of that, the top 10 holders control 88.7% of the supply, meaning a small number of wallets could move a very large share of tokens at once, and liquidity is not locked, so whoever controls the liquidity pool could withdraw it, reducing the ability to sell at a meaningful price.
It's important to be clear about what this check does not do. It reads contract mechanics only — it does not assess who is behind the project, whether the team has a track record, how the tokenomics are structured long-term, whether there is any legal entity attached, or what the stated intent of the token is. A low score here reflects unverifiable or concentrated contract-level conditions on the date checked, not a judgement about the people running the project or their plans. Likewise, no flags being raised on a given function does not mean that function is absent — it may simply mean the data source didn't report it, as is the case here for several core checks.
Given the unverified source code, concentrated holder base, and unlocked liquidity, someone looking into OMN further would reasonably want to look at the deployer wallet's history and whether it has deployed similar unverified contracts before, check whether the liquidity pool tokens are held by a known locker contract or sit in a single wallet, and see if the project has published verified source code elsewhere or has plans to. It would also be worth monitoring whether the top holders are exchange or team wallets with vesting versus unrelated individual addresses, since concentration alone doesn't say who holds it. None of this changes the automated findings, but it fills in context the contract mechanics alone can't 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 10 points out of 100.
A deep check also reviews the project's public materials, team, tokenomics and disclosures.