More than one contract on ethereum (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.
0x16a3832e690278d4979fd072fa4913bd1e8cbfd8same
open
2 of 2 sources are protocol-attested — a contract confirmed this link.
| registry | +3 | {"tx":"0xa265f3f912dc3b97cf9e13591e514ea422b23354643603b0e0d91b1e7b66bdec","from":"bridge_pin"} |
| derivation | +5 | {"via":"remoteToken","adapter":"base_bridge"} |
0x1258d60b224c0c5cd888d37bbf31aa5fcfb7e870
open
1 of 1 sources are protocol-attested — a contract confirmed this link.
| derivation | +5 | {"via":"remoteToken","adapter":"base_bridge","l2Chain":"base","l2Token":"0x16a3832e690278d4979fd072fa4913bd1e8cbfd8"} |
0x16a3832e690278d4979fd072fa4913bd1e8cbfd8same
open
Every source here is an inference. A contract on this chain has not confirmed the link itself.
| same_address | +3 | {"chain":"ethereum"} |
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.
No transfer has been seen leaving base.
| Pin | Received | Bridge | Bridge tx | Outcome | Discovery took |
|---|---|---|---|---|---|
| #7248 | 2 d ago | base_bridgeethereum → base | 0x7047d523…f9ae2d | SKIPPED_DUPLICATE | 9 h |
Every address above came from an on-chain read. The evidence trail shows which read produced it.