wSTATE

name unknown

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

Lifecycle

first pin received 2026-09-06 13:59:14 UTC · 20 h ago #9305 via layerzero
token discovered 2026-09-05 12:33:06 UTC · 2 d ago 3 contracts today
first liquid 2026-09-07 08:22:09 UTC · 2 h ago a chain quoted liquid
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.

solana canonical via layerzero 1

gcc7qfmgy9rkvdp8wdkqguvzpwubhzddfugitgevirt open

illiquidno route found

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

discord

{"notes":[],"proven":false,"ticker":"wSTATE","source_tx":null,"message_id":"1390943350105964626","message_ts":"2025-07-05T06:32:17","source_url":"https://layerzeroscan.com/address/0x1f3938E52b6821CF73020D1f40bB30753B951807","message_url":"https://discord.com/channels/1341185540162195456/1341864130071498792/1390943350105964626","source_kind":"oft_address","curator_liquidity":true}

solana mint burn via layerzero decimals differ from source potential · no transfer seen 5

Gcc7QfMgy9rKVdp8wdKqgUvzPWubHzDDfugiTgEvirt open

liquid251 bps · 2.51% via jupiter

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

peer_map

{"via":{"address":"0x1f3938e52b6821cf73020d1f40bb30753b951807","chainSlug":"base"},"adapter":"layerzero","oftStore":"9JmGxbhZTBVQVqs57CpyUZ94sVsnyYsxKVvZs6CdU6E1","resolvedMint":"Gcc7QfMgy9rKVdp8wdKqgUvzPWubHzDDfugiTgEvirt"}

base canonical via layerzero 4

0x1f3938e52b6821cf73020d1f40bb30753b951807 open

illiquidpools hold $0, under the floor

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

discord	+1	{"notes":[],"proven":false,"ticker":"wSTATE","source_tx":null,"message_id":"1390943350105964626","message_ts":"2025-07-05T06:32:17","source_url":"https://layerzeroscan.com/address/0x1f3938E52b6821CF73020D1f40bB30753B951807","message_url":"https://discord.com/channels/1341185540162195456/1341864130071498792/1390943350105964626","source_kind":"oft_address","curator_liquidity":false}
registry	+3	{"tx":"0xb003ad5149b08a9bdd62bce5cab492b8456081e9d4c4847057f61ca727c60cca","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 0xb003ad51… 20 h ago

from solana 1 of 1 reachable

base layerzero 4ksFdNnKtx… 20 h ago

Pins behind this token

Pin	Received	Bridge	Bridge tx	Outcome	Discovery took
#9305	20 h ago	layerzerobase → solana	0xb003ad51…c60cca	DISCOVERED	8 min

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.