2
3 contracts on 2 chains · 3 routes via LZLayerZero2 contracts on avalanche. 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
decimals differ
added
0x50327c6c…f87ab5
open
avalanche
mint burn · via layerzero
confirmed
2 on this chain
0x24de8dcc…17ba3a
open
0x1cec7490…756197strong +5avalanche
canonical · via layerzero
confirmed
2 on this chain
added
0xc5718c4c…01dcd1
open
| Lane | Bridge | Evidence | Proof | Last seen |
|---|---|---|---|---|
ethereum 0x50327c6c…f87ab5 → avalanche 0x24de8dcc…17ba3a |
LZLayerZero | confirmed | 0x1cec7490…756197 | 2 mo ago |
ethereum 0x50327c6c…f87ab5 → avalanche 0xc5718c4c…01dcd1 |
LZLayerZero | confirmed | 0xa0fe0a08…8423ac | 2 mo ago |
avalanche 0xc5718c4c…01dcd1 → ethereum 0x50327c6c…f87ab5 |
LZLayerZero | confirmed | 0x5f650102…88a8b6 | 2 mo ago |
Add another bridge transaction. Every transfer you paste re-checks the contracts on both ends and adds the route it proves.