More than one contract on base (3). 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.
0xb9caa63e09c646c1ec79acb2158d173e64a5fed3
open
2 of 2 sources are protocol-attested — a contract confirmed this link.
| registry | +3 | {"tx":"0x29df1ef4fb22e0b81c8fef28b5eb50fccc259c888371e400e89f25f1d96f72cb","from":"bridge_pin"} |
| derivation | +5 | {"via":"remoteToken","adapter":"base_bridge"} |
0x00c83aecc790e8a4453e5dd3b0b4b3680501a7a7
open
1 of 1 sources are protocol-attested — a contract confirmed this link.
| derivation | +5 | {"via":"remoteToken","adapter":"base_bridge","l2Chain":"base","l2Token":"0xb9caa63e09c646c1ec79acb2158d173e64a5fed3"} |
0x91d00cf7be6f47bf9bfaaa974d80ea79a4a3bfe7
open
Every source here is an inference. A contract on this chain has not confirmed the link itself.
| bridge_transfer | +5 | {"tx":"0xb15cfbc0718fd086905d4cb5b21a09b2dc653883b1df338c0954a425e01e97fb","adapter":"base_bridge"} |
0xb49a02585e2beb912027d8876dc1cdbe8f97c1a3
open
Every source here is an inference. A contract on this chain has not confirmed the link itself.
| bridge_transfer | +5 | {"tx":"0x2baab72088a3722bc7829a27e90d82cb235f6f2a81db2d93173b77d1622cc404","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 |
|---|---|---|---|---|---|
| #7174 | 2 d ago | base_bridgeethereum → base | 0x74b4a8b4…564024 | SKIPPED_DUPLICATE | 3 h 59 min |
| Kind | Created | State | Sent | Telegram id |
|---|---|---|---|---|
| multi_chain_liquid | 10 h ago | SENT | 10 h ago | 741 |
Every address above came from an on-chain read. The evidence trail shows which read produced it.