Which address is the real one

On 28 August 2026 this chain carried 542 contracts with “Robinhood Token” in the name. 194 of them are real. Search for the ticker AAPL and 1,130 contracts answer, four of them carrying Apple's name in the issuer's style and three of those reproducing the bullet in “Apple • Robinhood Token”, and only one of the four carries the dividend. The counts move, so every figure here is dated.

What does not work as a test

• The ticker. One ticker, over a thousand answers.
• The name. 348 contracts wear the issuer naming convention without being it. Among them several NVIDIA, a Tesla, about a dozen GameStop, an Eli Lilly, a Trump Media.
• The presence of a symbol or decimals. Anyone can set those.

What does work

A real Robinhood wrapper is a 283 byte proxy that reads its implementation from a single beacon contract. Both facts are readable without any trust:

const code = await rpc('eth_getCode', [address, 'latest']);
const size = (code.length - 2) / 2;                 // 283 for the real ones
const real = size === 283 &&
  code.toLowerCase().includes('e10b6f6b275de231345c20d14ab812db62151b00');

Everything else on this chain that claims the name fails one of those two checks. The catch is obvious: to apply the test you already have to know which beacon is the right one, which is the kind of fact a register is supposed to hold for you.

The nine that have received an action

Out of 194 real wrappers, these are the only addresses that have ever had a corporate action applied. Every one is verified by the bytecode test above. Multipliers are the live values on 28 August 2026 at block 48,447,297.

Only WEEK and CRWD carry counts that are not what they look like: one of WEEK's five is a correction and one is a repeat, and CRWD's second entry is the same event logged twice. SGOV's two are simply two accruals, a month apart. Telling those cases apart is what the event model exists for.

Fields

{
  "ticker": "AAPL",
  "address": "0xaf3d76f1834a1d425780943c99ea8a608f8a93f9",
  "issuer": "robinhood",
  "kind": "beacon_proxy",
  "bytecode_size": 283,
  "implements_erc8056": true,
  "can_receive_action": true,
  "ui_multiplier": "1.000566080",
  "actions_applied": 1,
  "checked_at": { "block": 48331252, "date": "2026-08-28" }
}

A contract that fails the test is not deleted from the map, it is published with can_receive_action: false. Knowing which addresses are dead ends is half the value.