zBTC

name unknown

status: unmeasured2/2 checked · 0 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 · 0 liquid · 1 unmeasured
checking: warm
already alerted on: nothing yet
pins: 1

Lifecycle

first pin received 2026-09-06 14:00:19 UTC · 22 h ago #9383 via layerzero
token discovered 2026-09-05 12:33:06 UTC · 2 d ago 3 contracts today
first liquid 2026-09-07 02:34:39 UTC · 10 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

zbtcug3er3tlyffelcvdnrkkcymbpwysgcwihesyflg no explorer

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":"zBTC","source_tx":null,"message_id":"1428043396295163954","message_ts":"2025-10-15T15:34:37","source_url":"https://layerzeroscan.com/address/0x81ccB38e4A7611a451Fd8439baD0f57812a227b6","message_url":"https://discord.com/channels/1341185540162195456/1341864130071498792/1428043396295163954","source_kind":"oft_address","curator_liquidity":true}

solana mint burn via layerzero potential · no transfer seen 5

zBTCug3er3tLyffELcvDNrKkCymbPWysGcWihESYfLg open

unknownRATE_LIMITED — not a negative result

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

peer_map

{"via":{"address":"0x81ccb38e4a7611a451fd8439bad0f57812a227b6","chainSlug":"binance"},"adapter":"layerzero","oftStore":"7NXgVoeAwZ1Q7XAThj15FpvMc8ZQUCNbsJxT3kWPzhbC","resolvedMint":"zBTCug3er3tLyffELcvDNrKkCymbPWysGcWihESYfLg"}

binance canonical via layerzero 4

0x81ccb38e4a7611a451fd8439bad0f57812a227b6 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":"zBTC","source_tx":null,"message_id":"1428043396295163954","message_ts":"2025-10-15T15:34:37","source_url":"https://layerzeroscan.com/address/0x81ccB38e4A7611a451Fd8439baD0f57812a227b6","message_url":"https://discord.com/channels/1341185540162195456/1341864130071498792/1428043396295163954","source_kind":"oft_address","curator_liquidity":false}
registry	+3	{"tx":"0xa31ec88220b2cb5876c9848b2cc1e1854b38bf08868181e8028b18481adae54e","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 binance 1 of 1 reachable

solana layerzero 0xa31ec882… 22 h ago

from solana 1 of 1 reachable

binance layerzero 5hwBAg6JEM… 22 h ago

Pins behind this token

Pin	Received	Bridge	Bridge tx	Outcome	Discovery took
#9383	22 h ago	layerzerobinance → solana	0xa31ec882…dae54e	DISCOVERED	19 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.