2
3 contracts on 2 chains · 4 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 ↓
binance
mint burn · via layerzero
confirmed
0xacf5a368…c92e13
open
ethereum
canonical · via layerzero
confirmed
2 on this chain
0xccdbb9c8…a475dd
open
ethereum
canonical · via layerzero
confirmed
2 on this chain
0x7a8caffe…4572e6
open
| Lane | Bridge | Evidence | Proof | Last seen |
|---|---|---|---|---|
ethereum 0xccdbb9c8…a475dd → binance 0xacf5a368…c92e13 |
LZLayerZero | confirmed | 0x45e58e6a…6b7f68 | 2 mo ago |
binance 0xacf5a368…c92e13 → ethereum 0xccdbb9c8…a475dd |
LZLayerZero | confirmed | 0xd9023fef…99bccb | 2 mo ago |
ethereum 0x7a8caffe…4572e6 → binance 0xacf5a368…c92e13 |
LZLayerZero | confirmed | 0xab395b46…e25220 | 2 mo ago |
binance 0xacf5a368…c92e13 → ethereum 0x7a8caffe…4572e6 |
LZLayerZero | confirmed | 0xac0047c7…ccf286 | 2 mo ago |
Add another bridge transaction. Every transfer you paste re-checks the contracts on both ends and adds the route it proves.