2
3 contracts on 2 chains · 3 routes via Base bridge2 contracts on base. 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 base_bridge
confirmed
added
0x9aab071b…a26fa5
open
base
mint burn · via base_bridge
confirmed
2 on this chain
added
0x37f0c291…3e064c
open
base
mint burn · via base_bridge
confirmed
2 on this chain
0x102a7fe0…711b78
open
0x6e440d07…a5e6b7strong +5| Lane | Bridge | Evidence | Proof | Last seen |
|---|---|---|---|---|
ethereum 0x9aab071b…a26fa5 → base 0x37f0c291…3e064c |
Base bridge |
confirmed | 0x80accdb7…1b0e76 | 2 mo ago |
base 0x37f0c291…3e064c → ethereum 0x9aab071b…a26fa5 |
Base bridge |
confirmed | 0x44500f04…f8ae36 | 2 mo ago |
ethereum 0x9aab071b…a26fa5 → base 0x102a7fe0…711b78 |
Base bridge |
confirmed | 0x6e440d07…a5e6b7 | 2 mo ago |
Add another bridge transaction. Every transfer you paste re-checks the contracts on both ends and adds the route it proves.
| Kind | Created | State | Sent | Rechecks | Outcome | Telegram |
|---|---|---|---|---|---|---|
| resend | 2 mo ago | SENT | 2 mo ago | 0 | — | 1401 |
| multi_chain_liquid | 2 mo ago | SENT | 2 mo ago | 0 | — | 435 |