first pin received2026-09-03 06:06:20 UTC · 2 d ago#7139 via debridge
token discovered2026-09-03 00:24:49 UTC · 2 d ago5 contracts today
first liquid2026-09-04 03:24:43 UTC · 27 h agoa chain quoted liquid
first alert2026-09-03 15:14:25 UTC · 2 d agomulti_chain_liquid, sent 2 d ago
reported chainsbinance, ethereum — 2 of 3
Where this token lives
More than one contract on ethereum (2), 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.
ethereummint burnvia debridgedecimals differ from source5
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":59649,"bridge":"debridge","reason":"discovery linked deployments across assets","candidates":["solana:Cy52Ts2GwSzdkhCihB5i1Vu6sApzgqktNNFyHbsdgwm7","ethereum:0x728f30fa2f100742c7949d1961804fa8e
{"pin":60250,"bridge":"debridge","reason":"discovery linked deployments across assets","candidates":["solana:BQyER2RMZB1c9WuxjG9P72faxdYtD94roz4gKyr3m2wV","binance:0xbd7b8e4de08d9b01938f7ff2058f110ee1
active
Every address above came from an on-chain read. The evidence trail shows which read produced it.