2
5 contracts on 4 chains · 10 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
mint burn · via layerzero
confirmed
2 on this chain
0xd10ddb7d…4c69f1
open
binance
mint burn
inferred
2 on this chain
0x776e4eab…7d2544same
open
ethereum
canonical · via layerzero
confirmed
0x2224e03c…b8c607same
open
polygon
mint burn · via layerzero
confirmed
0x2224e03c…b8c607same
open
base
canonical · via layerzero
confirmed
0x776e4eab…7d2544same
open
| Lane | Bridge | Evidence | Proof | Last seen |
|---|---|---|---|---|
ethereum 0x2224e03c…b8c607 → polygon 0x2224e03c…b8c607 |
LZLayerZero | confirmed | 0x511d8d15…d9a332 | 2 mo ago |
polygon 0x2224e03c…b8c607 → ethereum 0x2224e03c…b8c607 |
LZLayerZero | confirmed | 0xa5562f41…9ba99f | 2 mo ago |
ethereum 0x2224e03c…b8c607 → base 0x776e4eab…7d2544 |
LZLayerZero | confirmed | 0x167b0e29…f828f5 | 2 mo ago |
polygon 0x2224e03c…b8c607 → base 0x776e4eab…7d2544 |
LZLayerZero | confirmed | 0x36103ee5…642689 | 2 mo ago |
ethereum 0x2224e03c…b8c607 → binance 0xd10ddb7d…4c69f1 |
LZLayerZero | confirmed | 0xbc4ae069…64f998 | 2 mo ago |
base 0x776e4eab…7d2544 → binance 0xd10ddb7d…4c69f1 |
LZLayerZero | confirmed | 0xd2c9df4b…358be2 | 2 mo ago |
binance 0xd10ddb7d…4c69f1 → base 0x776e4eab…7d2544 |
LZLayerZero | confirmed | 0x8ed2e53b…0e7ce0 | 2 mo ago |
polygon 0x2224e03c…b8c607 → binance 0xd10ddb7d…4c69f1 |
LZLayerZero | confirmed | 0xa01490a7…dedff0 | 2 mo ago |
binance 0xd10ddb7d…4c69f1 → polygon 0x2224e03c…b8c607 |
LZLayerZero | confirmed | 0x6f92635c…50363e | 2 mo ago |
base 0x776e4eab…7d2544 → polygon 0x2224e03c…b8c607 |
LZLayerZero | confirmed | 0xbdc464b8…05be22 | 2 mo ago |
Add another bridge transaction. Every transfer you paste re-checks the contracts on both ends and adds the route it proves.