More than one contract on avalanche (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.
0x3fe4902b275caf603c46c81f3d921bb8515b5bc0
open
1 of 1 sources are protocol-attested — a contract confirmed this link.
| peer_map | +5 | {"via":{"address":"0x9d549c39e5e1a0e7ef41d4b7d74c49f976102e36","chainSlug":"sonic"},"adapter":"layerzero"} |
0x9d549c39e5e1a0e7ef41d4b7d74c49f976102e36same
open
1 of 1 sources are protocol-attested — a contract confirmed this link.
| registry | +3 | {"tx":"0xd7e1e0766aaece8dfb456369c5e9ce5f8fd6106df312472df2a3c85f7eb78b06","from":"bridge_pin"} |
0x9d549c39e5e1a0e7ef41d4b7d74c49f976102e36same
open
Every source here is an inference. A contract on this chain has not confirmed the link itself.
| same_address | +3 | {"chain":"avalanche"} |
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.
| Pin | Received | Bridge | Bridge tx | Outcome | Discovery took |
|---|---|---|---|---|---|
| #6802 | 2 d ago | layerzerosonic → avalanche | 0xd7e1e076…b78b06 | DISCOVERED | 3 h |
Every address above came from an on-chain read. The evidence trail shows which read produced it.