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.
0xaf9fe3b5ccdae78188b1f8b9a49da7ae9510f151
open
2 of 2 sources are protocol-attested — a contract confirmed this link.
| registry | +3 | {"tx":"0x730e000c4c475d2984706a0bf88e07fef387b1102be7e19297febe04a33f65a7","from":"bridge_pin"} |
| derivation | +5 | {"via":"remoteToken","adapter":"optimism_bridge"} |
0xca1207647ff814039530d7d35df0e1dd2e91fa84
open
5 of 5 sources are protocol-attested — a contract confirmed this link.
| derivation | +5 | {"via":"remoteToken","adapter":"optimism_bridge","l2Chain":"optimism","l2Token":"0xaf9fe3b5ccdae78188b1f8b9a49da7ae9510f151"} |
| registry | +3 | {"tx":"0x3e2014625c402370d874253ba85be4ec09ba3277c346a1ef396a0dc94d7464e8","from":"bridge_pin"} |
| derivation | +5 | {"via":"pin_source","adapter":"polygon_bridge","rootChainManager":"0xa0c68c638235ee32657e8f720a23cec1bfc77c77"} |
| registry | +3 | {"tx":"0x27e20f1bdb7868fd4f5c5a67a90ab80694f532b9872773328b0428b0f8677e48","from":"bridge_pin"} |
| derivation | +5 | {"via":"pin_source","adapter":"base_bridge"} |
0x8c92e38eca8210f4fcbf17f0951b198dd7668292
open
1 of 1 sources are protocol-attested — a contract confirmed this link.
| derivation | +5 | {"via":"rootToChildToken","adapter":"polygon_bridge","rootChainManager":"0xa0c68c638235ee32657e8f720a23cec1bfc77c77"} |
0x8ae125e8653821e851f12a49f7765db9a9ce7384
open
Every source here is an inference. A contract on this chain has not confirmed the link itself.
| bridge_transfer | +5 | {"tx":"0xa47c3ce687d9ed820acec8380372c035e925bf6d628075c91d248c2e90e425c2","adapter":"base_bridge"} |
0x54bc229d1cb15f8b6415efeab4290a40bc8b7d84
open
Every source here is an inference. A contract on this chain has not confirmed the link itself.
| bridge_transfer | +5 | {"tx":"0x3c34b3945ae1a56fa623382f7c89d6fef63f2fa09c9cede5f2474d534bf4c78a","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.
No transfer has been seen leaving polygon.
| Pin | Received | Bridge | Bridge tx | Outcome | Discovery took |
|---|---|---|---|---|---|
| #6961 | 2 d ago | base_bridgeethereum → base | 0x27e20f1b…677e48 | DISCOVERED | 3 h 35 min |
| Kind | Created | State | Sent | Telegram id |
|---|---|---|---|---|
| chain_added | 18 h ago | SENT | 18 h ago | 673 |
| multi_chain_liquid | 27 h ago | SENT | 27 h ago | 298 |
Every address above came from an on-chain read. The evidence trail shows which read produced it.