Trade with care. Read the warnings first.
A test sale worked on the Uniswap V3 pool, but we couldn't finish testing another pool.
- WARNHoneypot
- WARNChecks with missing data
- WARNFunding lineage
DexProof recorded PIPEDOG as CAUTION on Robinhood Chain under formula v2.0.1, in verdict #1649 published 30 Oct 2026 (UTC). Of 28 checks, 23 passed, 3 warned and 2 could not be run.
Trade with care. Read the warnings first.
A test sale worked on the Uniswap V3 pool, but we couldn't finish testing another pool.
Price
$0.0005
Liquidity
$3.72M
Volume 24h
$29,857
FDV
$5.79M
Buys 24h
41
68 sells
Age
94d 3h
A test sale worked on the Uniswap V3 pool, but we couldn't finish testing another pool.
At least one pool did not pass its sell test and could not be shown too small to matter, so we can't say this token can be sold everywhere. That result covers one pool only, so it does not show this token can be sold everywhere. Sells on this pool go through a swap hook we could not verify. Our code check found no owner-set sell controls, but that does not show what the hook does to a sale.
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.
This deployer is a new wallet funded by another new wallet, a common setup before a rug.
These are gaps in what we could see, not problems found in this token.
We couldn't read this pool's liquidity history, so we couldn't check who holds its liquidity.
This pool is on Uniswap V3 and holds 100.0% of the liquidity we could read. 2 other pools charge a fee too large to trade through, so nothing a holder owns is at risk there.
Launched on an unregistered launchpad, but we don't know how that launchpad works, so we can't say whether there was a raise for the creator to buy into.
This token does not share its name and symbol with any real tokenized share.
The explorer has not tagged this contract as a scam.
This token's creator removed only small amounts from its own pool (once, each under 0.1% of supply), and nothing larger.
Other wallets removed liquidity from it 3111 times, so this does not mean the pool is intact. The creator's recent history has 2 removal calls. These calls alone do not show which pools were involved.
Nothing on record ties , the wallet that funded the creator, to a past rug on Robinhood Chain.
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.
This deployer has no earlier launches on record.
Top 10 holders hold 13% of the tokens in circulation.
Against total supply, the top 10 hold 8.7%. Liquidity pools hold 32.4% 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.
The contract has no owner function, so it has no single owner wallet.
The deepest pool holds $3,721,249.
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.
This token's value at full supply is 2× its pool liquidity, a proportionate ratio.
We found no privileged powers in the token contract's code.
We looked at its audited source and compiled code.
Trading volume over 24 hours is 0.0× the pool's liquidity, below our warning level.
Volume is 0.0× the pool's liquidity, below our warning level.
Our market data had no trader counts, so we could not check for wallets trading back and forth.
We saw no fee or limit changes by the deployer in the transactions we searched.
We only looked at the deployer's recent history, so changes by a separate fee owner would not show.
No active paid boosts.
DexScreener has paid listing services on record for this token (a token profile), which is common for a launched token.
This token's code doesn't match any code template we know of.
This token's pool was 94 days old at this scan.
This contract was 94 days old at this scan.
The source is verified, so anyone can read the code.
We could not match it to a known template.