Markets
Discovered by counting transfers, not from a list
A pasted token list is right on the day it was pasted and silently wrong after the next listing. This counts Transfer events over 16 sampled windows spread across 1,200,000 blocks of chain, ranks contracts by how much they are actually used, and reads the top slice back as ERC-20s. Head block 56,019,222.
| Symbol | Name | Decimals | Transfers |
|---|---|---|---|
| USDG | Global Dollar | 6 | 28,664 |
| WETH | WETH | 18 | 25,603 |
| HOOD | HOOD | 18 | 4,161 |
| TSLA | Tesla • Robinhood Token | 18 | 2,655 |
| SPY | SPDR S&P 500 ETF Trust • Robinhood Token | 18 | 2,034 |
| PLTR | Palantir Technologies • Robinhood Token | 18 | 1,420 |
| PONS | Pons | 18 | 1,096 |
| RIM | Reaction Injection Molding | 18 | 1,048 |
| NVDA | NVIDIA • Robinhood Token | 18 | 1,027 |
| NEST | Nest | 18 | 895 |
| WARCAT | WARCAT | 18 | 808 |
| RIMCOIN | RIMCOIN | 18 | 807 |
| SPCX | Space Exploration Technologies Corp. Class A … | 18 | 807 |
| QQQ | Invesco QQQ • Robinhood Token | 18 | 785 |
| GLD | SPDR Gold Trust • Robinhood Token | 18 | 642 |
| 🅿️ | Pushin' 🅿️ | 18 | 638 |
| P | P | 18 | 607 |
| MSTR | Strategy Inc. • Robinhood Token | 18 | 491 |
| META | Meta Platforms • Robinhood Token | 18 | 396 |
| MU | Micron Technology • Robinhood Token | 18 | 344 |
| GOOGL | Alphabet Class A • Robinhood Token | 18 | 309 |
| GME | GameStop • Robinhood Token | 18 | 289 |
| AAPL | Apple • Robinhood Token | 18 | 249 |
| MSFT | Microsoft • Robinhood Token | 18 | 214 |
| USAR | USA Rare Earth • Robinhood Token | 18 | 200 |
| BABA | Alibaba • Robinhood Token | 18 | 173 |
| AMZN | Amazon • Robinhood Token | 18 | 164 |
| AMC | AMC Entertainment • Robinhood Token | 18 | 161 |
| USO | United States Oil Fund • Robinhood Token | 18 | 149 |
| SLV | iShares Silver Trust • Robinhood Token | 18 | 144 |
| TTWO | Take-Two Interactive Software • Robinhood Tok… | 18 | 133 |
| SGOV | iShares 0-3 Month Treasury Bond • Robinhood T… | 18 | 119 |
| IBM | IBM • Robinhood Token | 18 | 111 |
| RDDT | Reddit • Robinhood Token | 18 | 110 |
Ticker is not identity
Several contracts here answer symbol() with the same famous letters
12 symbol collisions were found among the 196 tokens read back, and they are recorded rather than resolved by picking the one with more supply. Tokenised equities are identified by the issuer suffix on their name(), anchored at the end and length-bounded — an unanchored substring test admitted a token whose name is 34,090 characters on a sibling site, because the suffix appeared somewhere inside it.
| Symbol | Contracts claiming it | Addresses |
|---|---|---|
| PONS | 3 | 0x39dbed3a… 0x709037cd… 0xf5c39d0e… |
| 🅿️ | 3 | 0xe1e5f00a… 0x2ff153ba… 0xed67738b… |
| AI | 3 | 0x2e8c3116… 0xeadd2ca8… 0x63fa26fb… |
| WATERMELON | 2 | 0xa2a3b4eb… 0x8fc95cad… |
| IBRN | 2 | 0xf6c9ce97… 0x6f59f478… |
| OZZY | 2 | 0x3c9b1677… 0xd85c0c5f… |
| IBM | 2 | 0x980dcf67… 0x960d816a… |
| GRACE | 3 | 0xce221b17… 0x9565828b… 0xf05babb8… |
| UP | 2 | 0x66b5a465… 0x57c0e45c… |
| POOH | 2 | 0x073408ab… 0xa2d93f34… |
| FINANCE | 2 | 0x9a8bec58… 0x37a94b5a… |
| PENKE | 2 | 0xcb240a86… 0xe2d8bc15… |
Rejected by the length bound on this run: 0. Zero is a normal outcome here — the read-back covers the most-transferred contracts, and the pathological ones are not among them — so this count is published rather than turned into a build failure it would fail for the wrong reason.
What the app can and cannot prove
Two tokens carry the verification, and the reason is a storage layout
Every build executes the app's own calldata against real tokens. Giving the run a balance means writing the token's balances mapping directly through a state override, and the slot is discovered rather than remembered — a candidate is overridden with a nonce and the token is asked what it thinks the balance is.
Exercised
- USDG — 6 decimals, balances slot 1, 7 checks
- WETH — 18 decimals, balances slot 51, 7 checks
A whole token in and a whole token back, to the wei, at block 56,022,198.
Not exercised
Nothing was skipped on this run.
The tokenised equities on this chain do not use a standard balances mapping at any slot below 128, so no balance can be fabricated for them and they cannot be part of this check. The app still deploys over them; it is the verification that cannot reach them, and saying so is the point of this panel.