Robinhood Chain · id 4663 · $404

mint() — 404.
pause() — 404.
blacklist() — 404.

Every token tells you it's safe. This reads the bytecode and tells you what's actually in it. Paste any Robinhood Chain address below — the scan runs in your browser against the chain, no server sits in the middle, and you can check the answer yourself with one eth_getCode.

bytecode scanner chain 4663 · connecting
>
awaiting input…

 

try:

What it looks for

the current signature set

Solidity puts every function's 4-byte selector into the dispatch table as a PUSH4 constant. The scanner walks the runtime bytecode opcode by opcode — skipping over push data so it can't be fooled by a selector that happens to sit inside a constant — and records which of these it finds.

SelectorSignatureWhy it matters

What it can't tell you

read this part

A scanner that always gives an answer is worth less than one that admits where it stops. This reports which functions exist in bytecode — never "safe", never "scam".

Proxies

A clean-looking proxy can point at vicious logic. The scanner reads the EIP-1967 implementation slot, follows it, and scans what actually executes — and says so in the output.

If it finds DELEGATECALL without a standard proxy slot, it stops short and reports inconclusive rather than clean.

Non-standard dispatch

Vyper and heavily optimised contracts don't always lay out selectors the usual way. Absence of a PUSH4 is evidence, not proof.

Everything off-chain

Liquidity that isn't burned, one wallet holding 60% of supply, a team that simply sells — none of that lives in bytecode, and none of it shows up here. A clean scan is one input, not a verdict.

Next: the same scan, on chain

Scanner.sol

The browser version is the convenient one. The verifiable one is a contract: scan(address) as a view function that EXTCODECOPYs the target and returns a flag word, so any wallet, bot or other contract can ask the same question without trusting this page or anyone running it. Free to call, impossible to fake, composable with anything.

FlagBitSet when
MINT0x01a mint selector is present in the executing code
PAUSE0x02pause / unpause present
BLACKLIST0x04any blacklist-family selector present
OWNER0x08ownership surface present and not renounced
UPGRADE0x10upgradeTo / upgradeToAndCall present
PROXY0x20EIP-1967 implementation slot is set
OPAQUE0x40DELEGATECALL with no resolvable target — scan is inconclusive

The token

scans clean on its own scanner

$404 is the tool's own dogfood: a plain ERC-20 whose whole pitch is a function call anyone can run against it. Scan the address above and the report is the marketing.

Specification

NameFunction Not Found
Symbol404
Decimals18
Supply1,000,000,000
ChainRobinhood Chain (4663)
Team allocation0
Transfer tax0%
Contractnot deployed

Expected report

mint  —  404
pause  —  404
blacklist  —  404
owner  —  404
upgradeTo  —  404

Anything else would make the name a lie, which is a useful property for a token to have.