More than one contract on base (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.
0xe2c31380bc22c6844951fdb8c29e5c20d395aa7e
open
1 of 1 sources are protocol-attested — a contract confirmed this link.
| peer_map | +5 | {"via":{"address":"0xb4e28e2a52116c3dcc3137f123d0543a8c9699ca","chainSlug":"robinhood"},"adapter":"layerzero"} |
0xb4e28e2a52116c3dcc3137f123d0543a8c9699casame
open
1 of 1 sources are protocol-attested — a contract confirmed this link.
| registry | +3 | {"tx":"0x230406334c6fa48e0261eec1588e43c4196e4905f86927379e3054ad30b6a355","from":"bridge_pin"} |
0xb4e28e2a52116c3dcc3137f123d0543a8c9699casame
open
Every source here is an inference. A contract on this chain has not confirmed the link itself.
| same_address | +3 | {"chain":"base"} |
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.
| Pin | Received | Bridge | Bridge tx | Outcome | Discovery took |
|---|---|---|---|---|---|
| #9092 | 25 h ago | layerzerobase → robinhood | 0x8a5e6d65…904eed | SKIPPED_DUPLICATE | 6 h |
| #9086 | 25 h ago | layerzerorobinhood → base | 0x23040633…b6a355 | DISCOVERED | 6 h |
Every address above came from an on-chain read. The evidence trail shows which read produced it.