Token Dashboard
tokens
2792
contracts
8856
confirmed
7212 of 8856
chains seen
14
unmeasured
105
queued
0

FIGHT

FIGHT
status
illiquid2/2 checked · 0 liquid · warm
first bridged
24 h ago
arrived via
layerzero
contracts
4 on 2 chains
confirmed by a transfer
3 of 4
liquidity
2 of 2 chains checked · 0 liquid
checking
warm
already alerted on
nothing yet
pins
1

Lifecycle

  1. first pin received 2026-09-06 14:00:52 UTC · 25 h ago #9413 via layerzero
  2. token discovered 2026-09-06 14:53:31 UTC · 24 h ago 4 contracts today
  3. first liquid pending not yet
  4. first alert pending not yet
  5. reported chains pending none yet

Where this token lives

More than one contract on solana (3). 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.

solana canonical via layerzero
potential · no transfer seen 1
9jxc4j1shw5segaucv9majjtedyxgbz2ckg65euqeqda open
illiquidpools hold $0, under the floor

Every source here is an inference. A contract on this chain has not confirmed the link itself.

discord+1{"notes":["**4 OFT**"],"proven":false,"ticker":"FIGHT","source_tx":null,"message_id":"1438033771050958918","message_ts":"2025-11-12T05:12:48","source_url":"https://layerzeroscan.com/address/0xBBA2117B21BCf8F67b1A83c60EeD01ae8528B063","message_url":"https://discord.com/channels/1341185540162195456/1341864130071498792/1438033771050958918","source_kind":"oft_address","curator_liquidity":false}
binance canonical via layerzero
1
0xbba2117b21bcf8f67b1a83c60eed01ae8528b063 open
illiquidpools hold $0, under the floor

Every source here is an inference. A contract on this chain has not confirmed the link itself.

discord+1{"notes":["**4 OFT**"],"proven":false,"ticker":"FIGHT","source_tx":null,"message_id":"1438033771050958918","message_ts":"2025-11-12T05:12:48","source_url":"https://layerzeroscan.com/address/0xBBA2117B21BCf8F67b1A83c60EeD01ae8528B063","message_url":"https://discord.com/channels/1341185540162195456/1341864130071498792/1438033771050958918","source_kind":"oft_address","curator_liquidity":false}
solana mint burn via layerzero
5
AmPaDQR5pogezB2d6zUw9oH9LAEM1DuhqSC8Bn8SCS6X open
illiquidpools hold $0, under the floor

Every source here is an inference. A contract on this chain has not confirmed the link itself.

bridge_transfer+5{"tx":"4svbjHF4D1VyjP9khzCpLjunKpTHGvzVrVTV3Fzps8CbQpKfPLGmQFVWNm8GFZYvb5kzmkRYX6KQFmj8WbUxJh7L","adapter":"layerzero"}
solana canonical via layerzero
8
9JXc4J1ShW5SegaUCV9majJTedyXgBz2CKg65eUqEQDa open
illiquidpools hold $0, under the floor

2 of 2 sources are protocol-attested — a contract confirmed this link.

registry+5{"tx":"3zrKzTDBS7ueW5SQRjQcMCsiexsjZqmBMibnX6p9x1VgXQNPUW5MVGdQKxQh6r9CrjdZUM74PEUUhWC7MCRbTMZG","via":"solana_tx_parse"}
registry+3{"tx":"3zrKzTDBS7ueW5SQRjQcMCsiexsjZqmBMibnX6p9x1VgXQNPUW5MVGdQKxQh6r9CrjdZUM74PEUUhWC7MCRbTMZG","from":"bridge_pin"}

How it moves between chains

Add another bridge transaction. Every transfer you paste re-checks the contracts on both ends and adds the route it proves.

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.

from binance 0 of 1 reachable

No transfer has been seen leaving binance.

show 1 unreachable hide unreachable
solana no transfer seen
from solana 1 of 1 reachable
binance layerzero 4svbjHF4D1… 24 h ago

Pins behind this token

PinReceivedBridgeBridge txOutcomeDiscovery took
#9413 25 h ago layerzerosolana → binance 3zrKzTDBS7…RbTMZG DISCOVERED 53 min

Merge history

WhenWinnerLoserContracts movedEvidenceState
24 h ago #2930 #2267 2 {"tx":"3zrKzTDBS7ueW5SQRjQcMCsiexsjZqmBMibnX6p9x1VgXQNPUW5MVGdQKxQh6r9CrjdZUM74PEUUhWC7MCRbTMZG","bridge":"layerzero","reason":"a delivered transfer connected contracts held by two assets","endpoint": active

Verdict. Add it if this is the token you want to watch; reject it if any contract is a twin, a clone or junk — a rejected token stays checked but is not alerted on again.

Exclude this token if it is junk or not worth watching. Liquidity stops being checked and nothing more is searched for it; its contracts, evidence, routes and history stay, its pins are still recorded, and it can be tracked again from the Excluded page.

Every address above came from an on-chain read. The evidence trail shows which read produced it.