Tokenized stocks · Robinhood Chain
Every ticker has a copy. This tells you which is which.
Of 31 tokens we found using 18 stock tickers, 17 share one thing none of the others do: the same contract code, pointed at the same beacon, and all 17 were created by the same factory contract. Those are the tokens named after a company with “• Robinhood Token” on the end. The rest are copies, most with a round billion supply and names like Advanced Micro Dog.
What the check is, and what it is not
- It reads the contract, not the name. A name is free to copy. A token that calls itself a Robinhood Token while failing the code check is the one this page warns about loudest.
- It checks who created the contract. On 10 October 2026 we read the creation of every token in our sample from an archive node. All 17 of the 17 family tokens were created through one contract, 0x4783…c046, which we call the StockFactory because that is the name in its own error message. None of the 14 copies were. A token with the family’s code and beacon that we can show was created outside the factory reads as an impostor. If we cannot read its creator, it is not shown as a match either: the row says the creator is not confirmed.
- The factory refused every stranger we tried. We simulated a real creation again, with a fresh id, from three other addresses: a burn address, our own wallet, and the deployer of one of the copies. The factory reverted all three. From the original account, 0x5516…e000, the same simulated call succeeds. We have not read the factory’s permission list, so we cannot rule out other permitted accounts.
- It cannot tell you who holds that account. We can show the factory, and that it accepted that account and refused the others we tried. We cannot show that account belongs to Robinhood. So a match reads “created by the StockFactory”, never “official” or “verified”.
- A contract we have not seen is read live, and says when it cannot be. Its creator is looked up through an archive node when one is configured and not already busy. If a pasted contract has the family’s code and beacon but we could not read its creator, it reads “family code and beacon, creator not confirmed”, not a match. A creator we failed to read never counts in a token’s favour, and never against it either: that row is not called an impostor.
- It does not print an exit cost. Our exit measurement still overstates thin markets. Telling you a token is the real one next to a number we know is too high would be two claims pulling against each other.