More than one contract on ethereum (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.
0xb4818bb69478730ef4e33cc068dd94278e2766cbsame
open
1 of 1 sources are protocol-attested — a contract confirmed this link.
| peer_map | +5 | {"via":{"address":"0x1958853a8be062dc4f401750eb233f5850f0d0d2","chainSlug":"ethereum"},"adapter":"layerzero"} |
0xb4818bb69478730ef4e33cc068dd94278e2766cbsame
open
1 of 1 sources are protocol-attested — a contract confirmed this link.
| peer_map | +5 | {"via":{"address":"0x1958853a8be062dc4f401750eb233f5850f0d0d2","chainSlug":"ethereum"},"adapter":"layerzero"} |
0x70654aad8b7734dc319d0c3608ec7b32e03fa162
open
1 of 1 sources are protocol-attested — a contract confirmed this link.
| peer_map | +5 | {"via":{"address":"0x1958853a8be062dc4f401750eb233f5850f0d0d2","chainSlug":"ethereum"},"adapter":"layerzero"} |
0xb4818bb69478730ef4e33cc068dd94278e2766cbsame
open
1 of 1 sources are protocol-attested — a contract confirmed this link.
| peer_map | +5 | {"via":{"address":"0x1958853a8be062dc4f401750eb233f5850f0d0d2","chainSlug":"ethereum"},"adapter":"layerzero"} |
0xb4818bb69478730ef4e33cc068dd94278e2766cbsame
open
Every source here is an inference. A contract on this chain has not confirmed the link itself.
| bridge_transfer | +5 | {"tx":"0xb0ff70a8e2f7cfa77c440700b0ee1783cb618a6030bea8f9d2e9043af34e28ac","adapter":"layerzero"} |
0x1958853a8be062dc4f401750eb233f5850f0d0d2
open
1 of 1 sources are protocol-attested — a contract confirmed this link.
| registry | +3 | {"tx":"0x2ce6e63166cd5745baf08635bad04309a65294ed94d6244d2f7926c8368f8c5d","from":"bridge_pin"} |
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 |
|---|---|---|---|---|---|
| #6651 | 2 d ago | layerzerobase → binance | 0xd0166720…5b6095 | SKIPPED_DUPLICATE | 2 h 30 min |
| Kind | Created | State | Sent | Telegram id |
|---|---|---|---|---|
| multi_chain_liquid | 2 h ago | SENT | 2 h ago | 784 |
Every address above came from an on-chain read. The evidence trail shows which read produced it.