Reading Robinhood Chain
Every new Robinhood Chain token, scored from evidence you can click.
The Deed Score adds up six checks on a token’s contract, deployer, holders and activity into a number from 0 to 100, and every point links to the on-chain or explorer evidence behind it.
It is evidence, not a safety guarantee or financial advice. Checks we could not verify score 0.
Recently launched, ranked by Deed Score
JSON feedNo blocks scanned yet.
- RPC log scan failed: An unknown RPC error occurred. (Cannot read properties of undefined (reading 'error')). Showing the last tokens we found.
How it works
1. Find
We watch recent blocks for ERC-20 tokens being minted for the first time and confirm each one answers the standard token calls.
2. Check
Six read-only checks run against the chain’s RPC and block explorer. Nothing is signed and no transactions are sent.
3. Show the proof
Each check is a row with pass, partial, fail or “could not verify”, a plain explanation, and a link to its evidence.
The six checks
Source verified 20 pts
Is the contract's source code published on the explorer?
Ownership 15 pts
Has owner() been renounced, or can one account still change things?
Transfer simulation 20 pts
Does a simulated transfer from the largest holder go through without a big hidden fee?
Deployer history 15 pts
What else has the deployer created, and how did it score?
Holder concentration 15 pts
How much of the supply sits in the top 10 wallets?
Real activity 15 pts
Are people other than the deployer actually moving the token?
Known limits
- “Could not verify” means the data was unavailable. It scores 0, which is not the same as failing.
- The transfer simulation is a single simulated transfer, not a full DEX sell test. It cannot catch every trap.
- A brand-new deployer has no history, so that check is unknown rather than bad.