What our one-sentence verdict is actually telling you

You paste a contract address into a scanner and you get back a short sentence. It reads like a judgement. It is not one. The question worth asking is what that sentence is made of, which parts of it are checkable facts, which parts are context, and where the edges of its knowledge are. This piece walks through the four questions the verdict answers, in the order it answers them, and then explains a design choice that surprises people: even on a bad read, we still show you where the token trades and how to buy it.

The verdict is a sequence, not a score

A score implies trade-offs. Good liquidity cancelling out a live mint authority, a strong chart offsetting a frozen pool. The four checks do not trade off against each other, because each one is a precondition for the next being worth reading.

Is it trading? If not, the other three answers are trivia about a dead contract. Can it be sold? If not, the fact that it is trading is close to irrelevant, because trading in one direction is not a market. Does the developer still hold the keys? If yes, everything above can change without warning. How far has it already run? Only once the first three are settled does the price history mean anything.

Read in that order, the sentence tells you where the risk sits. Read as a single word, it tells you almost nothing.

One: is it trading

This is the plainest check. Is there an active market right now — pools with balances in them, swaps happening, a token that has not been deployed and abandoned. A market cap is just the last traded price multiplied by the supply; on a token nobody trades, that number is an arithmetic artefact, not a valuation. A token can hold a large-looking market cap for months with a handful of transactions behind it. Trading is the difference between a price and a number.

Two: can it be sold

Buying and selling are not the same permission, and the buy side of a contract is almost never the restricted one. A token can have deep-looking pools and still be hard or impossible to exit: transfer restrictions that block addresses the contract has not approved, a sell tax that is far higher than the buy tax, liquidity that is unlocked and can be withdrawn, or a pool whose only meaningful holder is the deployer. The read asks whether a sell path exists and what it costs to use it.

It cannot promise the sell path will still be there tomorrow. A contract that permits selling today can be changed, or its liquidity can be removed, after you have entered. That is a limit of any snapshot, ours included.

Three: does the developer still hold the keys

Most of what people call a rug is a permission, not an accident. Mint authority means someone can create more supply and dilute what you hold. Freeze authority means someone can freeze the tokens sitting in your wallet. Ownership of the liquidity pool means someone can withdraw the assets that give the token its price. Control over fee parameters means the cost of selling can be raised after you buy.

"Renounced" is a word used loosely in marketing. The useful question is narrower: which specific permissions are still live, and who can exercise them. A contract with no live authorities is not thereby safe — it can still go to zero — but the mechanism by which the developer can act against holders is gone, and that is worth knowing separately.

Four: how far has it already run

Only here does price history enter, and the honest way to present it is as a distribution rather than a direction.

Across the Solana calls we have logged — 36,176 of them — 52.4% were flat or down from the market cap at the moment we logged them. 21.3% doubled, 6.4% reached five times, 2.6% reached ten times, and 0.3% reached fifty times. On Robinhood Chain the picture differs by category: of 8,150 meme tokens, 5.6% doubled; of 3,974 unclassified tokens, 5.0% doubled; of 868 stock-paired tokens, 16.0% doubled; of 639 utility tokens, 27.5% doubled. These figures are as of 2026-09-15.

Two things about how those numbers were built matter more than the numbers. They are forward-measured from our own logged calls: the entry is the market cap when we logged the token, and the peak is measured only after that moment, never before. And the tokens that went nowhere are included in every total. Remove them and the percentages stop meaning anything.

The practical lesson is arithmetic, not prophecy. If a token has already run, your entry sits at a higher market cap than the one that ran, and the distance to a similar multiple is correspondingly longer. That is a fact about where you are standing, not a statement about where the price goes next.

Why the buy route is never hidden

People sometimes expect a scanner to withhold the trading route when the read is bad. We do the opposite. The route and the risk appear side by side, and the bad reads keep the route.

Three reasons. The information is public: the pools, the contract, the venues are all visible to anyone with a block explorer, so hiding the route does not remove access, it only removes the warning attached to it. Second, a withheld route makes the read look like a permission slip — as if the tool opening the door were an endorsement. The verdict is a description of a token's current state, not approval. Third, a verdict that only appears when the answer is good is a marketing device, not a read, and you would be right not to trust one.

So a bad read shows you the contract, the pool, the live authorities, the risk sentence, and the way to trade it anyway. You may have reasons we cannot see. What you should not have is a missing warning.

What the verdict does not tell you

It does not tell you what price you will get, or what the market does next. It does not see news, unlock schedules, or a developer's intentions. It is a snapshot: a contract can be altered after the read, and the read will not know. On Robinhood Chain, 3,974 tokens fall outside our categories — "unclassified" means we could not place it, not that it is bad and not that it is fine, only that we have less context. And nothing here speaks to position sizing, which depends on your circumstances and is not a question a scanner can answer.

##