HOW TO READ IT

Three steps,
and five markers

The desk asks a contract what its deployed code still allows and prints the answers. No rating invented out of nothing, and no suggestion to act — every line is a reading, and every reading names where it came from.

Three steps

no account, no wallet

01 Give it an address

Pick a chain — a working endpoint is filled in for you — and paste the contract. If you know the pair it trades in, paste that too; without it the liquidity reading says so rather than guessing.

02 Read the colours

Red is a power somebody else holds over your balance. Green is that power being absent from the code. Amber means the desk failed to look, and says why. Click any row for the function behind it.

03 Set your own rules

The switches under the verdict are yours. The dial counts how many of them the contract passed — turn one off and the number moves, because it scores your rules and not the token.

The markers

⚠A power over somebody else’s balance, or a rule of yours that was broken. Whoever holds the key can use it without asking you.

·A reading with no direct effect on your balance — a size, a share, a figure.

○A power that is absent: the function is not in the deployed code at all.

?Not checked, with the reason. A fact about the desk, never about the token — an endpoint that refused is not a contract that is clean.

✎Only the command line can answer this: it needs a document fetched and a model called.

Two profiles

Coin — runs here

Twelve readings, all from bytecode and storage
No documents, because a coin has none
Everything is read for the contract you named, at a named block
Nothing is stored about you and no wallet is ever asked for

Documents — command line

The eight legal slots need the issuer’s files, which a browser cannot fetch across origins
They also need a model — and a model that proposes a claim must not be the thing that approves it
The files are hashed and kept, so a quote can be checked against the bytes actually read
A quote that is not in the document is deleted whole and printed as rejected

What it will not do

What it does

Reads the deployed bytecode and storage, and reports what it found
Names the function each reading came from, so you can check it yourself
Says plainly when it failed to look, and why
Refuses a pool that does not trade the token you asked about
Counts concentration only over balances somebody could decide to sell

What it does not

No rating of the token, no verdict, no suggestion to act
Never asks for a wallet, a key, a signature or a transaction
Does not simulate a trade, so it cannot tell you a sale would fail
Does not know who deployed the contract, or anything off-chain
A contract that reads clean can still be emptied by whoever holds the supply

Three steps,and five markers