Trade with care. Read the warnings first.
Top 10 holders hold 79% of the tokens in circulation.
Scanned 2d ago. Scan again before you trade.
- FAILHolder concentration
- WARNChecks with missing data
DexProof recorded COMPANY as CAUTION on Robinhood Chain under formula v2.0.1, in verdict #1338 published 28 Oct 2026 (UTC). Of 28 checks, 15 passed, 1 warned, 1 failed and 11 could not be run.
Trade with care. Read the warnings first.
Top 10 holders hold 79% of the tokens in circulation.
Scanned 2d ago. Scan again before you trade.
Price
—
Liquidity
—
Volume 24h
—
FDV
—
Buys 24h
—
Age
—
Top 10 holders hold 79% of the tokens in circulation.
The largest holder is , a plain wallet, holding 17.5% of the tokens in circulation on its own. Against total supply, the top 10 hold 1.8%. Liquidity pools hold 89.5% of total supply, and we leave them out of the tokens in circulation. The top 10 share also moves when pool liquidity moves, even if no holder trades. A further 8.2% of total supply is in a permanent launchpad locker with no withdrawal path. It can never re-enter circulation, so we leave it out of the tokens in circulation.
We couldn't work out who controls this token's liquidity on this scan.
Missing data limits the verdict. A pool we couldn't read is not a pool we cleared. This describes what we could see, not the token.
These are gaps in what we could see, not problems found in this token.
Applies to: Deployer pulled liquidity, Funder rug history, Deployer launch history, Funding lineage, Tax manipulation
So we can't read the creator's transactions. We can't rule out that the creator pulled liquidity.
So we can't check for past rugs, because many people launch through it. The launchpad's own record names , but that address is a contract too, not a person's wallet, so we don't attribute any history to that address.
So we can't check its past launches. The launchpad's own record names , but that address is a contract too, not a person's wallet, so we don't attribute any history to that address.
So we can't trace who funded it. The launchpad's own record names , but that address is a contract too, not a person's wallet, so we don't attribute any history to that address.
So we can't check whether it changed fees or limits.
We couldn't read this pool's liquidity history, so we couldn't check who holds its liquidity.
This pool is on Uniswap V4 and holds 100.0% of the liquidity we could read.
We could not read this token's market data, so we did not measure its pool depth.
That is a gap in what we could see, not a finding about the token.
We don't have the market data needed to compare this token's value at full supply with its liquidity.
We don't have the volume and liquidity figures needed to check turnover.
We don't have the market data needed to check for wash trading.
We could not find when this token's pool was created.
This token does not share its name and symbol with any real tokenized share.
The explorer has not tagged this contract as a scam.
The token's main pool and every other pool large enough to matter let it be sold in our test.
1 hook-free pool is too small to matter and was set aside. This does not show how large a sale those pools can absorb, or that Uniswap's own router will carry it out. A new wallet can also send this token to the pool, the transfer a sell actually makes. A price quote alone can't test that.
This token is not on our list of confirmed rugs.
This token has no honeypot mark in our records.
This token has no pump-and-dump mark in our records.
The contract has no owner function, so it has no single owner wallet.
This contract's code is fixed.
We found no standard upgrade setup on it.
This contract's source is verified on the explorer, but it was matched from another address with identical bytecode, not proven against this one.
We found no privileged powers in the token contract's code.
We looked at its audited source and compiled code. This is about the token contract only. Its main pool runs the Pons V2 Meme Hook, which can take up to 10% of each trade.
No paid promotion found on DexScreener.
This token's code doesn't match any code template we know of.
This contract was 59 days old at this scan.
Launched on Pons V2 and graduated to a DEX pool.
The trades on its curve were not recorded, so how much of the raise the creator bought is unknown. We couldn't fully read the transaction that opened this token's pool, so we don't know who bought at launch.
The source is verified, so anyone can read the code.
We could not match it to a known template.