LiLLy

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

Lifecycle

first pin received 2026-09-03 23:02:17 UTC · 17 h ago #9125 via layerzero
token discovered 2026-09-03 23:02:23 UTC · 17 h ago 3 contracts today
first liquid pending not yet
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.

hyperevm canonical via layerzero 10

0xf2e6a23b1aa09565fdb3a77af7772709de3f4f95 open

illiquidno route found

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

peer_map	+5	{"via":{"address":"0x543697e4753fa7e00e1839110e41749b7c9e2c29","chainSlug":"robinhood"},"adapter":"layerzero","oftAdapter":"0x543697e4753fa7e00e1839110e41749b7c9e2c29","unwrappedTo":"0xf2e6a23b1aa09565fdb3a77af7772709de3f4f95"}
peer_map	+5	{"via":{"address":"0xd51fdf3d83d4c17c802df06040ab51e66a923e95","chainSlug":"robinhood"},"adapter":"layerzero","oftAdapter":"0x7f47f40d296e0c06f07457a3d4f5551e2070a171","unwrappedTo":"0xf2e6a23b1aa09565fdb3a77af7772709de3f4f95"}

robinhood canonical via layerzero 3

0x543697e4753fa7e00e1839110e41749b7c9e2c29 open

illiquidpools hold $0, under the floor

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

registry

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

robinhood canonical via layerzero shadowed · not checked 3

0xd51fdf3d83d4c17c802df06040ab51e66a923e95 open

not checked yet

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

registry

{"tx":"0x3ad464f46bbe0b7d04010b1a0e391e0c50cb843dd85a90048d6bf68ad7dea8c6","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 hyperevm 1 of 1 reachable

robinhood layerzero 0x3b072170… 9 h ago

from robinhood 1 of 1 reachable

hyperevm layerzero 0x62385f43… 9 h ago

Pins behind this token

Pin	Received	Bridge	Bridge tx	Outcome	Discovery took
#9144	9 h ago	layerzerorobinhood → hyperevm	0x3ad464f4…dea8c6	DISCOVERED	10 s
#9126	17 h ago	layerzerohyperevm → robinhood	0x6857290b…69a5ad	SKIPPED_DUPLICATE	7 s
#9125	17 h ago	layerzerorobinhood → hyperevm	0x62385f43…a58312	DISCOVERED	6 s

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