Initialising agent
Run the agent The problem Live sample Method Signals Coverage $HSN
Autonomous verification · Live on Robinhood Chain

Verify the contract,not the ticker.

Robinhood Chain is permissionless — anyone can deploy a token there without KYC, including one that borrows the name of an asset you already trust. Hyper Ship Network reads the address itself: issuer authority, transfer hooks, approval traps, oracle state, liquidity depth. Then it gives you a verdict, before you sign.

Read-only·No wallet connection·No approvals requested
Scroll
4663Robinhood Chain ID
Arbitrum Orbit · ETH gas
100msBlock time
full EVM equivalence
200+Tokenised stocks & ETFs
tracked for impersonation
26Signals per verification
contract · market · counterparty
0Permissions required
read-only, never signs
Why an agent, why now

A new chain shipped with old scam tactics already waiting.

Robinhood Chain went live on 1 July 2026 with 200-plus tokenised stocks, Uniswap liquidity and Chainlink feeds — and a permissionless deployer surface reaching 23 million retail users. Within days, the failure modes were documented.

RISK 01

Tokens that delete themselves

Relay Protocol flagged advanced honeypots on the chain that remove holdings from the buyer's wallet after purchase — hidden transfer logic that burns or claws back balances, or drains through the approval granted during the swap. Funds spent are effectively unrecoverable.

Relay warning, 10 Jul 2026
RISK 02

The ticker is not the asset

Anyone can deploy a contract on the chain without KYC, so a token can imitate a legitimate issuer or a real Stock Token symbol. When Robinhood's own CEO account was hijacked in July to push a token, the lesson was blunt: a trusted name in front of a contract proves nothing about the contract.

Impersonation after the X hack
RISK 03

Structural risk, not just scams

Even legitimate Stock Tokens carry mechanics worth reading: an ERC-8056 UI multiplier that integrators can apply twice, an oraclePaused flag that is advisory rather than enforced on-chain, one authorised party controlling every mint and redeem, and a single sequencer ordering all of it.

Attack-vector breakdown
Live sample

Watch it read a contract.

Three shapes you will actually meet, on loop: a token impersonating an authorised Stock Token, the real one it copies, and an upgradeable proxy on mainnet. Same signals every time — three very different verdicts.

Run your own verification
Agent · live sample chain 4663
0
Pass 01

Resolve

Takes a raw address, ENS name, or a ticker you were shown. Determines what it actually is on-chain — token, proxy, EOA, or safe — and on which chain, then pins the exact contract behind the symbol rather than trusting the symbol.

bytecode classproxy targetEIP-1967 slotschain routing
Pass 02

Read

Pulls the state that decides whether you can ever get out: who holds mint, burn, pause and blocklist authority, whether the implementation is upgradeable and by whom, what the transfer path does beyond moving a balance, and how ownership is distributed.

admin keysupgradeabilitytransfer hooksholder graph
Pass 03

Simulate

Runs the trade you were about to run — buy, hold, then sell — against forked state. A honeypot that hides behind clean-looking source has to reveal itself here: reverting sells, punitive tax on exit, balances that shrink after the block, approvals that move more than you offered.

sell pathexit taxpost-buy balance deltaapproval scope
Pass 04

Cross-check

Compares the contract against the official issuer set for tokenised assets, so a symbol that looks like a real Stock Token but was deployed by an unrelated wallet is named as impersonation. Oracle freshness and pause state are read directly, along with Uniswap depth and how locked it really is.

issuer registrysymbol collisionoracle stalenessLP depth & lock
Pass 05

Report

Weights every signal into one credibility score from 0 to 100 and writes the verdict in plain language — what is wrong, how badly, and what would have to change for the score to move. Each line links back to the evidence. The agent never signs, never holds funds, never asks for an approval.

weighted scoreper-signal evidenceplain-language verdictshareable report
What it checks

Twenty-six signals, in four families.

Grouped the way losses actually happen: the contract traps you, the token lies about what it is, the market cannot absorb your exit, or the counterparty behind it has done this before.

Contract integrity

8 signals
Mint authority renouncedWhether any key can still inflate supply after you are holding.
No clawback or burn-fromOwner-gated burns that take balances straight out of a holder’s wallet.
Pause & freeze authorityA single key able to halt transfers and strand you mid-position.
Implementation immutableReads EIP-1967 slots — clean code means nothing if it can be swapped tomorrow.
Proxy admin distributionWhether upgrade power sits behind a multisig and a timelock, or one hot wallet.
Custom transfer hooksLogic on the transfer path that can claw back, burn, or redirect after purchase.
BlocklistsAn allow/deny list that can quietly stop you, specifically, from selling.
Honeypot sell simulationSimulated buy → sell against forked state. If the exit reverts, it is named outright.

Token authenticity

6 signals
Issuer registry matchDoes the deployer belong to the authorised issuer set for this asset, or is it unrelated?
Symbol & name collisionContracts imitating real Stock Token tickers, look-alike unicode, and near-miss names.
Metadata consistencyName, symbol and decimals agreeing with each other and with the issuer’s record.
Multiplier sanityChecks uiMultiplier() handling so a double-applied ERC-8056 multiplier cannot misprice what you see.
Oracle freshnessWhen the feed last updated, and how far it has drifted from spot.
Oracle pause stateWhether oraclePaused is set — a flag that is advisory, not enforced on-chain.

Market structure

6 signals
Liquidity depthReal Uniswap depth measured against your intended size, not against one token.
LP lock or burnWhether liquidity can be removed, by whom, and when the lock expires.
Holder concentrationMaps top wallets and clusters ones that move together — a coordinated exit is one wallet in effect.
Same-block insider bundlesLaunch-block accumulation that quietly positions you as the exit liquidity.
Exit slippage modelWhat leaving actually costs at the size you were going to take.
Wash-trading detectionWhether the volume drawing you in comes from distinct wallets or circular flow.

Counterparty history

6 signals
Deployer trailEvery prior deployment by the same wallet, and what became of each one.
Funding pathWhere the deployer’s gas came from: a long-lived wallet, a fresh bridge, or a mixer.
Drainer bytecode matchThe contract checked against known drainer sets and unbounded-approval solicitation.
Contract ageHow long this code has existed, weighted against everything else on the list.
Flagged wallet proximityEdges — direct or one hop — to addresses already tied to losses.
Bridge & withdrawal exposureL2 exit assumptions: the fraud-proof window and the single-sequencer dependency.
Agent, not a checklist

Doing this by hand takes forty minutes you don't have.

Verifying it yourself

  • Open a block explorer, find the contract, hope the source is verified and readable.
  • Manually diff the symbol against the real issuer's deployment — if you know where that list lives.
  • You cannot simulate a sell, so honeypot logic stays invisible until you try to exit.
  • Proxy admin, transfer hooks and oracle pause state require reading Solidity under time pressure.
  • By the time you finish, the entry you were checking has moved — so most people skip the check.
≈ 40 min · partial coverage · skipped under pressure

Running the agent

  • Paste the address or the ticker you were shown. It resolves the real contract for you.
  • Impersonation is checked against the authorised issuer set, not against your memory.
  • The exit is simulated before you own anything — reverting sells and exit taxes surface first.
  • All 26 signals every time, including the boring ones you would rationalise skipping.
  • One score, a written verdict, and the evidence behind each line so you can argue with it.
Under 3s · full coverage · read-only, never signs
Coverage

Robinhood Chain first. The whole L2 stack next.

The agent is EVM-native. Robinhood Chain is the priority surface because it pairs a permissionless deployer set with the largest retail distribution in the space — but the same reader runs anywhere the bytecode is EVM.

Robinhood ChainID 4663 · Orbit
Full · Stock Token aware
EthereumID 1 · mainnet
Full
Arbitrum OneID 42161
Full · settlement layer
BaseID 8453
Full
OptimismID 10
Queued
UnichainID 130
Queued
Polygon PoSID 137
Queued
BNB ChainID 56
Queued
$HSN · ERC-20

Verification as a public good, owned by the people using it.

$HSN is the access and alignment layer for the agent. Holding it opens deeper verification, watchlists on deployers you don't trust, and alerts the moment a contract you hold changes state.

Unlimited deep verifications, including full simulation traces
Deployer watchlists with real-time alerts on new launches
State-change alerts on any contract you already hold
Signal weighting governed by holders, published openly
Contract address · Ethereum
Not yet deployed — verify here first, on launch

$HSN is a utility and governance token for access to the agent. It is not an investment product and confers no claim on revenue or assets.

Hyper Ship Network mark

One paste, or one empty wallet.

Verification takes about as long as reading this sentence. Signing takes less — and it's the only one of the two you can't undo.