3
4 contracts on 2 chains · 2 routes via LZLayerZero3 contracts on ethereum. 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
canonical · via layerzero
confirmed
added
0xfceb31a7…9edc46
open
ethereum
canonical · via layerzero
inferred
3 on this chain
0x03b36151…bc7860
open
ethereum
canonical · via layerzero
inferred
3 on this chain
0xaabdb196…0f23ba
open
ethereum
mint burn · via layerzero
confirmed
3 on this chain
0x11632069…d1933b
open
0x84e844f3…fe3943strong +5| Lane | Bridge | Evidence | Proof | Last seen |
|---|---|---|---|---|
binance 0xfceb31a7…9edc46 → ethereum 0x11632069…d1933b |
LZLayerZero | confirmed | 0x84e844f3…fe3943 | 2 mo ago |
ethereum 0x11632069…d1933b → binance 0xfceb31a7…9edc46 |
LZLayerZero | confirmed | 0x36c6ae09…1336e9 | 2 mo ago |
Add another bridge transaction. Every transfer you paste re-checks the contracts on both ends and adds the route it proves.