first pin received2026-09-06 14:00:25 UTC · 24 h ago#9390 via portal_bridge
token discovered2026-09-05 12:33:06 UTC · 2 d ago4 contracts today
first liquidpendingnot yet
first alertpendingnot yet
reported chainspendingnone yet
Where this token lives
More than one contract on solana (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.
solanacanonicalvia portal_bridge2
ejxvsnadfzchknlqxnuj3fx6ed2wqyci59pq9vs4tsv6no explorer
illiquidpools hold $0, under the floor
Every source here is an inference. A contract on this chain has not confirmed the link itself.
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.
{"pin":-1428061792,"bridge":"portal_bridge","reason":"discovery linked deployments across assets","candidates":["binance:0x72e56880a7b00df8fdf3ff9adf30e58a8fcf75a2","base:0x10a06cc1d223e2af76f985d0e54
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.