When these tokens pay you, your balance does not change.
Your position grows. The number your wallet shows you does not.
Read-only. Nothing to connect, nothing to sign, no key ever asked for.
Every published contract on chain 4663
One of them, read just now
A report is a transcript, not a verdict.
Every finding carries the call that produced it, pinned to a block. Re-run it against your own node and see whether we told you the truth.
Read a contractOr start from the 194 tokenized equities there
Reading the chain…
A live reading, taken when you loaded this page. Not a screenshot.
Where the number goes.
And what one write reaches.
Eight checks. Each one states what it cannot see.
- contract.exists
- Is there a contract at this address, and how large is its code?
- proxy.detect
- Does this contract hold its own logic, or forward to logic held elsewhere?
- token.identity
- What does this contract call itself, and how much of it exists?
- erc8056.multiplier
- Does the meaning of a balance here change without the balance changing?
- code.provenance
- What exactly is this code, and was it the same a short while ago?
- proxy.blast
- If the logic can be replaced, what else is replaced at the same time?
- admin.authority
- Who is able to change this contract, and is that a person or a contract?
- powers.selectors
- What powers are compiled into the code at this address?
No score. Ever. A score is an opinion you are asked to trust, and “we could not determine this” carries the same weight as any answer.
How you check us.
Step 1
The block is pinned first.
Every call names one block, so a report cannot contradict itself.
Step 2
Checks learn only through a recorder.
A finding cannot exist without the calls that produced it.
Step 3
The output is a pure function.
Same address, same block, byte-identical report, whoever runs it.
Step 4
You re-run it where we cannot reach.
The verifier replays every call from your browser against your node.
What we cannot see.
Found nothing is not the same as there being nothing.
- Logic behind a proxy — the stub is all there is to scan.
- Who holds a role — that lives in event history we do not read.
- Intent. A mint function is a capability, not a plan.
- Source against bytecode — that needs a service we do not integrate.
The complete list, per check →Reasonable objections →What the token is for →
Where this actually is.
Working now
Eight checks, recorded evidence, the wallet view, the registry, the diff, the watchlist, the badge, and in-browser re-verification against any endpoint.
Written, not deployed
The bonded-claim contract. It holds money and it is unaudited, and unaudited contracts do not hold money. No address exists.
Not built
Telling you a contract changed while you were not looking. That needs a scheduler and somewhere to send it.
Check something you were about to trust.
A boring answer is a good outcome, and you get the transcript either way.