first pin received2026-09-06 14:00:52 UTC · 25 h ago#9413 via layerzero
token discovered2026-09-06 14:53:31 UTC · 24 h ago4 contracts today
first liquidpendingnot yet
first alertpendingnot yet
reported chainspendingnone 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.
solanacanonicalvia layerzeropotential · no transfer seen1
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.
{"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.
Every address above came from an on-chain read. The evidence trail shows which read produced it.