2
3 contracts on 2 chains · 4 routes via LZLayerZero2 contracts on base. A wrapper beside the canonical is normal; a clone reusing the ticker looks the same. The one a transfer confirmed outranks the one matched by symbol. Compare below ↓
binance
mint burn · via layerzero
confirmed
0x22b1458e…c731fa
open
0x3ad39970…c90cfestrong +5base
mint burn · via layerzero
confirmed
2 on this chain
0x4c2413a7…072d15
open
0xa0611ed0…c53f3cstrong +5base
canonical · via layerzero
confirmed
2 on this chain
0x491cc54c…de9da1
open
| Lane | Bridge | Evidence | Proof | Last seen |
|---|---|---|---|---|
binance 0x22b1458e…c731fa → base 0x491cc54c…de9da1 |
LZLayerZero | confirmed | 0x17677935…362502 | 41 d ago |
base 0x491cc54c…de9da1 → binance 0x22b1458e…c731fa |
LZLayerZero | confirmed | 0x7b59ed3c…ed26f5 | 41 d ago |
base 0x4c2413a7…072d15 → binance 0x22b1458e…c731fa |
LZLayerZero | confirmed | 0x461c2fea…bafef0 | 2 mo ago |
binance 0x22b1458e…c731fa → base 0x4c2413a7…072d15 |
LZLayerZero | confirmed | 0x030c1fe9…d32486 | 2 mo ago |
Add another bridge transaction. Every transfer you paste re-checks the contracts on both ends and adds the route it proves.