2
4 contracts on 3 chains · 3 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 ↓
binance
canonical · via layerzero
confirmed
2 on this chain
0x1b3dc4da…acac51
open
binance
canonical · via layerzero
confirmed
2 on this chain
0x1b600603…de5c02
open
ethereum
canonical · via layerzero
confirmed
0x229e0bb6…fcd558
open
base
canonical · via layerzero
confirmed
0x88b77551…acdd2b
open
| Lane | Bridge | Evidence | Proof | Last seen |
|---|---|---|---|---|
ethereum 0x229e0bb6…fcd558 → binance 0x1b3dc4da…acac51 |
LZLayerZero | confirmed | 0xa0f5f804…614749 | 2 mo ago |
binance 0x1b600603…de5c02 → base 0x88b77551…acdd2b |
LZLayerZero | confirmed | 0xecae0834…7da6c6 | 2 mo ago |
base 0x88b77551…acdd2b → binance 0x1b600603…de5c02 |
LZLayerZero | confirmed | 0x2205c276…97ab5d | 2 mo ago |
Add another bridge transaction. Every transfer you paste re-checks the contracts on both ends and adds the route it proves.