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.
0xc52fafdc900cb92ae01e6e4f8979af7f436e2eb2
open
2 of 2 sources are protocol-attested — a contract confirmed this link.
| registry | +3 | {"tx":"0xb0b5fc0a69cfe588216e6c29535b4bdf85049afe8101cf8cf038b27e9961d3a7","from":"bridge_pin"} |
| derivation | +5 | {"via":"pin_source","adapter":"base_bridge"} |
0x395ae52bb17aef68c2888d941736a71dc6d4e125
open
Every source here is an inference. A contract on this chain has not confirmed the link itself.
| bridge_transfer | +5 | {"tx":"0x70078a9e7fe73fb3f6f2de20a3b4fde1303036a86cf21848b8fc711acb6595b7","adapter":"base_bridge"} |
0xd1917629b3e6a72e6772aab5dbe58eb7fa3c2f33
open
Every source here is an inference. A contract on this chain has not confirmed the link itself.
| bridge_transfer | +5 | {"tx":"0xf0b392cfc98d5e4805ba2ea55855f95f6d5640d5530fc46bd337f99f6d645685","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.
No transfer has been seen leaving base.
| Pin | Received | Bridge | Bridge tx | Outcome | Discovery took |
|---|---|---|---|---|---|
| #7884 | 2 d ago | base_bridgeethereum → base | 0xb0b5fc0a…61d3a7 | DISCOVERED | 10 h |
Every address above came from an on-chain read. The evidence trail shows which read produced it.