2
5 contracts on 4 chains · 1 routes via 
deBridge2 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 ↓
ethereum
mint burn · via debridge
confirmed
added
0x10dea674…54d800
open
binance
canonical · via debridge
confirmed
2 on this chain
added
0x30c60b20…94fc61
open
binance
canonical
inferred
2 on this chain
0x1f36ecf1…c0c2c8same
open
base
canonical
inferred
0x1f36ecf1…c0c2c8same
open
unichain
canonical
inferred
0xfa6f161a…8e1371
open
| Lane | Bridge | Evidence | Proof | Last seen |
|---|---|---|---|---|
binance 0x30c60b20…94fc61 → ethereum 0x10dea674…54d800 |
deBridge |
confirmed | 0x6945db50…6df143 | 2 mo ago |
ethereum 0x10dea674…54d800 → binance 0x30c60b20…94fc61 |
deBridge |
possible | debridge_adapter | 2 mo ago |
Add another bridge transaction. Every transfer you paste re-checks the contracts on both ends and adds the route it proves.