More than one contract on base (2). That is allowed — a bridge wrapper and the canonical token are separate contracts and trade in separate pools (§3) — but it is also what a clone reusing the ticker looks like. Compare the evidence below: a contract confirmed by the bridge itself outranks one matched only by symbol.
0xd101dcc414f310268c37eeb4cd376ccfa507f571
open
2 of 2 sources are protocol-attested — a contract confirmed this link.
| registry | +3 | {"tx":"0x8f450444f12e60e2f51e88ead29c88634b5b2fbfcb4a68873d57a15432e0fe57","from":"bridge_pin"} |
| derivation | +5 | {"via":"pin_source","adapter":"base_bridge"} |
0x4c47d80e73ce141423a39ca278ca1f1119666d38
open
Every source here is an inference. A contract on this chain has not confirmed the link itself.
| bridge_transfer | +5 | {"tx":"0xa18b8609df295ee022df0a874d81c9ca4641de57027c5047959ce8e7edcd56d0","adapter":"base_bridge"} |
0xfbb75a59193a3525a8825bebe7d4b56899e2f7e1
open
Every source here is an inference. A contract on this chain has not confirmed the link itself.
| bridge_transfer | +5 | {"tx":"0xf6cf2231b89265ce01a6f77c27e476324be130651e909defafef08bb702a8024","adapter":"base_bridge"} |
Each chain lists the directions a transfer has actually been seen taking. Directions with no transfer behind them are folded away per card and counted in its header. Derived routes are not shown at all.
| Pin | Received | Bridge | Bridge tx | Outcome | Discovery took |
|---|---|---|---|---|---|
| #8924 | 2 d ago | base_bridgeethereum → base | 0x33df4671…c82b1f | SKIPPED_DUPLICATE | 15 h |
| #7089 | 2 d ago | base_bridgebase → ethereum | 0x53846386…c285db | SKIPPED_DUPLICATE | 3 h 53 min |
| #4706 | 2 d ago | base_bridgebase → ethereum | 0x8fafb1e7…1aad43 | SKIPPED_DUPLICATE | 3 h 39 min |
Every address above came from an on-chain read. The evidence trail shows which read produced it.