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 ↓
base
mint burn · via base_bridge
confirmed
2 on this chain
added
0xfbb75a59…e2f7e1
open
0xf6cf2231…2a8024strong +5base
mint burn · via base_bridge
confirmed
2 on this chain
0x4c47d80e…666d38
open
0xa18b8609…cd56d0strong +5ethereum
canonical · via base_bridge
confirmed
added
0xd101dcc4…07f571
open
| Lane | Bridge | Evidence | Proof | Last seen |
|---|---|---|---|---|
base 0xfbb75a59…e2f7e1 → ethereum 0xd101dcc4…07f571 |
Base bridge |
confirmed | 0x8fafb1e7…1aad43 | 2 mo ago |
ethereum 0xd101dcc4…07f571 → base 0xfbb75a59…e2f7e1 |
Base bridge |
confirmed | 0xf6cf2231…2a8024 | 2 mo ago |
ethereum 0xd101dcc4…07f571 → base 0x4c47d80e…666d38 |
Base bridge |
confirmed | 0xa18b8609…cd56d0 | 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 |
|---|---|---|---|---|---|---|
| multi_chain_liquid | 2 mo ago | SENT | 2 mo ago | 0 | — | 968 |