2
4 contracts on 3 chains · 2 routes via LZLayerZero2 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 ↓
ethereum
canonical · via layerzero
confirmed
2 on this chain
0xb59478f5…637057
open
ethereum
mint burn · via layerzero
inferred
2 on this chain
0x838e0094…dbf488
open
binance
mint burn · via layerzero
confirmed
0xd454921a…d244e4
open
polygon
mint burn · via layerzero
confirmed
0xec23a1cb…e00e53
open
| Lane | Bridge | Evidence | Proof | Last seen |
|---|---|---|---|---|
ethereum 0xb59478f5…637057 → polygon 0xec23a1cb…e00e53 |
LZLayerZero | confirmed | 0x9040be1b…138467 | 2 mo ago |
ethereum 0xb59478f5…637057 → binance 0xd454921a…d244e4 |
LZLayerZero | confirmed | 0x60d304c2…349ac6 | 2 mo ago |
Add another bridge transaction. Every transfer you paste re-checks the contracts on both ends and adds the route it proves.