ROBINHOOD CHAIN · ID 4663 · 10 BLOCKS / SECOND
THE EDGE IS REAL.
IT DIES IN
ONE SECOND.
One wallet on the Robinhood Chain buys launchpad tokens and is right often enough to matter: 42% of its entries double. Six benches read the chain, scored 147 of them, and brute-forced 852,096 exit rules over the price paths. Then the same desk measured what copying it actually costs — and the answer is the whole story.
THE LIVE DESK
Six benches, one operator log, real RPC calls leaving your browser. The block stream and the price are live; every computed number carries the timestamp it was computed at.
THE DELAY CLIFF
The same rule, the same entries — only the delay between the leader's print and yours changes. This is the finding the rest of the desk exists to support.
Verdict from the clerk bench: fix routing before sizing up.
SIX BENCHES
Each bench does one job and hands its output to the next. Click one to read what it actually does.
TAP
Reads the chain.
THE SCORECARD
147 entries scored from the leader's own fill price, over 156 tokens and 588 transfers, between 2026-08-29 and 2026-09-05.
852,096 EXIT RULES
Every ladder × stop × time-stop × trailing combination replayed over the recorded price paths, in 80 seconds. Ranked three ways, because ranking by expected value alone rewards fragile rules.
| RANK | RULE | EV | MEDIAN | WIN | PF | MAX DD | PICKED FOR |
|---|
THE CHAIN
Everything below is read from the Robinhood Chain in your browser as you look at it. No backend, no cache — if a number moves while you read, that is the chain moving.
ADDRESS INSPECTOR
The genealogist bench's first question about any address, runnable by you: is it a person, a contract, or a wallet that delegated itself to code under EIP-7702?
METHOD & LIMITS
Which numbers here are live and which are computed once?
How were the entries scored?
Why is 147 entries not enough?
Is this a copy-trading signal?
Can I read the code?
chaindesk holds the six agents, the RPC layer and the decoder, with 27 offline
tests. The dashboard in this page is the same desk rendered from that pipeline's snapshot.