DexProof recorded RNODE as CAUTION on Robinhood Chain under formula v2.0.1, in verdict #1559 published 29 Oct 2026 (UTC). Of 28 checks, 16 passed, 2 warned, 1 failed and 9 could not be run.
Trade with care. Read the warnings first.
Top 10 holders hold 56% of the tokens in circulation.
Scanned 1d ago. Scan again before you trade.
Price
—
Liquidity
—
Volume 24h
—
FDV
—
Buys 24h
—
Age
—
Top 10 holders hold 56% of the tokens in circulation.
The largest holder is , a plain wallet, holding 12.7% of the tokens in circulation on its own. Against total supply, the top 10 hold 8.5%. Liquidity pools hold 76.6% 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 finish the sell test on the other exchanges we checked.
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. 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.
These are gaps in what we could see, not problems found in this token.
The creator's wallet was funded by , a shared source that has sent starting funds to 5 different wallets.
A shared source such as an exchange funds many unrelated people, so its record does not name any one of them.
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. One other pool charges a fee too large to trade through, so nothing a holder owns is at risk there.
This deployer was funded by , a wallet that has sent starting funds to 5 different wallets.
That is a shared source such as an exchange, so its history says nothing about this deployer.
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.
A contract created this token, so we can't see the person behind it.
So we can't check whether it changed fees or limits.
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.
No liquidity removal by the wallet recorded as this token's creator from its own pool.
Other wallets removed liquidity from it once, so this does not mean the pool is intact. The creator's recent history has no removal calls either.
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.
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 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 contract was 41 days old at this scan.
Launched on Pons V2 and graduated to a DEX pool.
The raise on record is too old to compare against, so how much of it 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.
Robinhood