More than one contract on binance (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.
0xfed13d0c40790220fbde712987079eda1ed75c51
open
1 of 1 sources are protocol-attested — a contract confirmed this link.
| registry | +5 | {"via":"TokenAdminRegistry","pool":"0xC78210649aF8A450C0f6E98107a0b614a3198359","adapter":"ccip","selector":"11344663589394136015"} |
0x6c76de483f1752ac8473e2b4983a873991e70da7same
open
1 of 2 sources are protocol-attested — a contract confirmed this link.
| registry | +3 | {"tx":"0xdf1a2a49e2a74e72268de82ed7501c2f90c97d0a5fad045222cfcbe762801558","from":"bridge_pin"} |
| discord | +2 | {"notes":[],"proven":true,"ticker":"BTR","source_tx":"0x5aa4358043d1a794b54440c7d0e1b6723eab1c99eed9c4ca17a7f8f6ab5261d1","message_id":"1397898777767186462","message_ts":"2025-07-24T11:10:40","source_url":"https://ccip.chain.link/#/side-drawer/msg/0x5aa4358043d1a794b54440c7d0e1b6723eab1c99eed9c4ca17a7f8f6ab5261d1","message_url":"https://discord.com/channels/1341185540162195456/1341864130071498792/1397898777767186462","source_kind":"ccip_msg","curator_liquidity":false} |
0x6c76de483f1752ac8473e2b4983a873991e70da7same
open
Every source here is an inference. A contract on this chain has not confirmed the link itself.
| same_address | +3 | {"chain":"binance"} |
| discord | +2 | {"notes":[],"proven":true,"ticker":"BTR","source_tx":"0x5aa4358043d1a794b54440c7d0e1b6723eab1c99eed9c4ca17a7f8f6ab5261d1","message_id":"1397898777767186462","message_ts":"2025-07-24T11:10:40","source_url":"https://ccip.chain.link/#/side-drawer/msg/0x5aa4358043d1a794b54440c7d0e1b6723eab1c99eed9c4ca17a7f8f6ab5261d1","message_url":"https://discord.com/channels/1341185540162195456/1341864130071498792/1397898777767186462","source_kind":"ccip_msg","curator_liquidity":false} |
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 |
|---|---|---|---|---|---|
| #7586 | 2 d ago | ccipethereum → binance | 0xf0915554…dc2686 | SKIPPED_DUPLICATE | 10 h |
| #7103 | 2 d ago | ccipbinance → ethereum | 0xd6d2c90b…b4ad5b | SKIPPED_DUPLICATE | 3 h 54 min |
| #6158 | 2 d ago | ccipbinance → ethereum | 0xd9a14e6b…873ec0 | SKIPPED_DUPLICATE | 43 min |
| #6042 | 2 d ago | ccipbinance → ethereum | 0xd7571cf2…22bf1f | SKIPPED_DUPLICATE | 1 h 6 min |
| #5981 | 2 d ago | ccipbinance → ethereum | 0xec6b4900…ac79a6 | SKIPPED_DUPLICATE | 1 h 17 min |
| #5908 | 2 d ago | ccipbinance → ethereum | 0xcf41185e…45d7ca | SKIPPED_DUPLICATE | 1 h 28 min |
| #5897 | 2 d ago | ccipbinance → ethereum | 0x54279d40…c27954 | SKIPPED_DUPLICATE | 1 h 30 min |
| #5777 | 2 d ago | ccipbinance → ethereum | 0xbdfd38cd…92cf50 | SKIPPED_DUPLICATE | 1 h 46 min |
| #5671 | 2 d ago | ccipbinance → ethereum | 0x5d36855b…50af13 | SKIPPED_DUPLICATE | 2 h |
| #5025 | 2 d ago | ccipbinance → ethereum | 0x5e498830…18b7dc | SKIPPED_DUPLICATE | 3 h 11 min |
| #5024 | 2 d ago | ccipbinance → ethereum | 0xa536070d…4fdeca | SKIPPED_DUPLICATE | 3 h 11 min |
| #5023 | 2 d ago | ccipbinance → ethereum | 0xd03bac1b…08792d | SKIPPED_DUPLICATE | 3 h 11 min |
| Kind | Created | State | Sent | Telegram id |
|---|---|---|---|---|
| multi_chain_liquid | 23 h ago | SENT | 23 h ago | 629 |
Every address above came from an on-chain read. The evidence trail shows which read produced it.