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.
0x7f05a7a9af2f5a07d1e64877c8dc37a64a22508e
open
2 of 2 sources are protocol-attested — a contract confirmed this link.
| registry | +3 | {"tx":"0x2fb4e923daea8d19e30e750318affaf828a7a0a0ad3baf0381d940dac6bcf4a5","from":"bridge_pin"} |
| derivation | +5 | {"via":"remoteToken","adapter":"base_bridge"} |
0x9a96ec9b57fb64fbc60b423d1f4da7691bd35079
open
1 of 1 sources are protocol-attested — a contract confirmed this link.
| derivation | +5 | {"via":"remoteToken","adapter":"base_bridge","l2Chain":"base","l2Token":"0x7f05a7a9af2f5a07d1e64877c8dc37a64a22508e"} |
0xd687e3c439c1caeebe0d1437d739b79d92a8d41f
open
Every source here is an inference. A contract on this chain has not confirmed the link itself.
| bridge_transfer | +5 | {"tx":"0x3a7ae6c89c2ed9d128aae59f6537624f8bc27a1af0a8d95adc258bb8d79e8cb6","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.
| Kind | Created | State | Sent | Telegram id |
|---|---|---|---|---|
| multi_chain_liquid | 21 h ago | SENT | 21 h ago | 474 |
Every address above came from an on-chain read. The evidence trail shows which read produced it.