2
4 contracts on 3 chains · 5 routes via LZLayerZero2 contracts on binance. 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 ↓
base
canonical · via layerzero
confirmed
0x7002987e…c222aa
open
binance
mint burn · via layerzero
confirmed
2 on this chain
0x582a560b…f066ec
open
binance
canonical
inferred
2 on this chain
0x6403af12…9c0558same
open
ethereum
mint burn · via layerzero
confirmed
0x6403af12…9c0558same
open
| Lane | Bridge | Evidence | Proof | Last seen |
|---|---|---|---|---|
ethereum 0x6403af12…9c0558 → binance 0x582a560b…f066ec |
LZLayerZero | confirmed | 0xacaf1d6d…cbab6d | 2 mo ago |
base 0x7002987e…c222aa → binance 0x582a560b…f066ec |
LZLayerZero | confirmed | 0xeb743685…f89933 | 2 mo ago |
base 0x7002987e…c222aa → ethereum 0x6403af12…9c0558 |
LZLayerZero | confirmed | 0x75718d51…58349b | 2 mo ago |
binance 0x582a560b…f066ec → base 0x7002987e…c222aa |
LZLayerZero | confirmed | 0xfcf360b8…75bc45 | 2 mo ago |
ethereum 0x6403af12…9c0558 → base 0x7002987e…c222aa |
LZLayerZero | confirmed | 0xabd202ec…eb74f8 | 2 mo ago |
Add another bridge transaction. Every transfer you paste re-checks the contracts on both ends and adds the route it proves.