MOCK

MockToken

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

Lifecycle

first pin received 2026-09-06 14:01:27 UTC · 26 h ago #9451 via layerzero
token discovered 2026-09-06 15:00:27 UTC · 25 h ago 3 contracts today
first liquid pending not yet
first alert pending not yet
reported chains pending none 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.

base canonical via layerzero 1

0x507530b96207e9190218bbdc27e0fd57454c685f 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

{"notes":["2nd OFT"],"proven":false,"ticker":"MOCK","source_tx":null,"message_id":"1448689371309019198","message_ts":"2025-12-11T14:54:21","source_url":"https://layerzeroscan.com/address/0xC05e3a1a1d1E5dcc5B3cBa9F19e6c103BA2E1a82","message_url":"https://discord.com/channels/1341185540162195456/1341864130071498792/1448689371309019198","source_kind":"oft_address","curator_liquidity":false}

solana canonical via layerzero potential · no transfer seen 1

dh9otawuch7wzygcskzcycnfythnd7ngthd8mrlap9hs no explorer

illiquidpools hold $0, under the floor

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

discord

solana canonical via layerzero 8

DH9otAWuCH7WZyGCsKZcycnfYThNd7nGTHD8mRLaP9hS open

illiquidpools hold $0, under the floor

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

registry	+5	{"tx":"5Cb9ximXf3WmJozFZaHL2e5L998c9JgCsiKpKnKk7ovS72fbWvpJc248hvC2oHLyT4euhAzRBuQdfD47doe1SurM","via":"solana_tx_parse"}
registry	+3	{"tx":"5Cb9ximXf3WmJozFZaHL2e5L998c9JgCsiKpKnKk7ovS72fbWvpJc248hvC2oHLyT4euhAzRBuQdfD47doe1SurM","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 base 1 of 1 reachable

solana layerzero 0x873d23e0… 25 h ago

from solana 1 of 1 reachable

base layerzero 5Cb9ximXf3… 25 h ago

Pins behind this token

Pin	Received	Bridge	Bridge tx	Outcome	Discovery took
#9451	26 h ago	layerzerosolana → base	5Cb9ximXf3…e1SurM	DISCOVERED	59 min

Merge history

When	Winner	Loser	Contracts moved	Evidence	State
25 h ago	#2934	#2336	2	{"tx":"5Cb9ximXf3WmJozFZaHL2e5L998c9JgCsiKpKnKk7ovS72fbWvpJc248hvC2oHLyT4euhAzRBuQdfD47doe1SurM","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.