LO0P

status: liquid2/2 checked · 1 liquid · warm
first bridged: 28 h ago
arrived via: layerzero
contracts: 3 on 2 chains
confirmed by a transfer: 3 of 3
liquidity: 2 of 2 chains checked · 1 liquid
checking: warm
already alerted on: nothing yet
pins: 2

Lifecycle

first pin received 2026-09-03 06:07:52 UTC · 2 d ago #8492 via layerzero
token discovered 2026-09-03 20:11:14 UTC · 28 h ago 3 contracts today
first liquid 2026-09-05 00:16:24 UTC · 7 min ago a chain quoted liquid
first alert pending not yet
reported chains pending none yet

Where this token lives

More than one contract on robinhood (2). That is allowed — a bridge wrapper and the canonical token are separate contracts and trade in separate pools (§3) — but it is also what a clone reusing the ticker looks like. Compare the evidence below: a contract confirmed by the bridge itself outranks one matched only by symbol.

ethereum canonical via layerzero 8

0x00000000000050806673b532d7486ac114c1de3f open

liquid398 bps · 3.98% via kyberswap

2 of 2 sources are protocol-attested — a contract confirmed this link.

registry	+3	{"tx":"0x9a5d5f12e5d4ef956fc51b6b1cb92b87824fe6a1d4814dce56c2d0301d669f40","from":"bridge_pin"}
peer_map	+5	{"via":{"address":"0x0cb0b973e6a98d558b21f1a330c44e91fb26efd2","chainSlug":"robinhood"},"adapter":"layerzero","oftAdapter":"0xa03d66c3aa5b9fd0cb82fd0e82d451d8a6f09ee8","unwrappedTo":"0x00000000000050806673b532d7486ac114c1de3f"}

robinhood mint burn via layerzero 5

0x29c1e9d49562572b9851b02bd4391a72933ede87 open

illiquidpools hold $0, under the floor

1 of 1 sources are protocol-attested — a contract confirmed this link.

peer_map

{"via":{"address":"0x9e44af4f7333c9d90d862d812cb59aa23f0f4182","chainSlug":"ethereum"},"adapter":"layerzero"}

robinhood canonical via layerzero shadowed · not checked 3

0x0cb0b973e6a98d558b21f1a330c44e91fb26efd2 open

illiquidpools hold $0, under the floor

1 of 1 sources are protocol-attested — a contract confirmed this link.

registry

{"tx":"0x5b7d0afeee8cbf034b072352ed65e2b92a2a79c03e860f4a6d644e3a0b7a7bca","from":"bridge_pin"}

How it moves between chains

Each chain lists the directions a transfer has actually been seen taking. Directions with no transfer behind them are folded away per card and counted in its header. Derived routes are not shown at all.

from ethereum 1 of 1 reachable

robinhood layerzero 0xc1a575d9… 28 h ago

from robinhood 1 of 1 reachable

ethereum layerzero 0x5b7d0afe… 28 h ago

Pins behind this token

Pin	Received	Bridge	Bridge tx	Outcome	Discovery took
#8522	2 d ago	layerzerorobinhood → ethereum	0x5b7d0afe…7a7bca	DISCOVERED	14 h
#8492	2 d ago	layerzeroethereum → robinhood	0x9a5d5f12…669f40	DISCOVERED	14 h

Every address above came from an on-chain read. The evidence trail shows which read produced it.