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.
0x1796ae0b0fa4862485106a0de9b654efe301d0b2same
open
2 of 2 sources are protocol-attested — a contract confirmed this link.
| registry | +3 | {"tx":"0x05c12a4f21409a08d0ec9e77571df75c0967458e1373080c13d84ded9d9dcd08","from":"bridge_pin"} |
| derivation | +5 | {"via":"pin_source","adapter":"base_bridge"} |
0xc4ba74d522a817797a0400024367099d1ab69c96
open
Every source here is an inference. A contract on this chain has not confirmed the link itself.
| bridge_transfer | +5 | {"tx":"0x605afcc2361e937c03f8c3310c325d11c2fafa2ac8a3836eb6c1d84fa5df8aba","adapter":"base_bridge"} |
0x60edae6e86546428da423b5fbe0fba46ca552fc7
open
Every source here is an inference. A contract on this chain has not confirmed the link itself.
| bridge_transfer | +5 | {"tx":"0x94231f10475ec9d0734c0eadd3352a15ed0819d3d3ced79b96229890ee06c245","adapter":"base_bridge"} |
0x1796ae0b0fa4862485106a0de9b654efe301d0b2same
open
Every source here is an inference. A contract on this chain has not confirmed the link itself.
| same_address | +3 | {"chain":"binance"} |
0x1796ae0b0fa4862485106a0de9b654efe301d0b2same
open
Every source here is an inference. A contract on this chain has not confirmed the link itself.
| same_address | +3 | {"chain":"polygon"} |
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 binance.
No transfer has been seen leaving polygon.
Every address above came from an on-chain read. The evidence trail shows which read produced it.