HYB

name unknown

status: illiquid2/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
checking: warm
already alerted on: nothing yet
pins: 1

Lifecycle

first pin received 2026-09-06 13:59:15 UTC · 20 h ago #9306 via layerzero
token discovered 2026-09-05 12:33:06 UTC · 2 d 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 binance (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.

binance mint burn via layerzero 6

0x6b81b498ae5c4f32de02fbbf535f3010808f8837 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":"HYB","source_tx":null,"message_id":"1391654060855263244","message_ts":"2025-07-07T05:36:23","source_url":"https://layerzeroscan.com/address/0x6f63D5ddbB40Cff27DcC92122D7f8b7C8F401048","message_url":"https://discord.com/channels/1341185540162195456/1341864130071498792/1391654060855263244","source_kind":"oft_address","curator_liquidity":false}
peer_map	+5	{"via":{"address":"0x6f63d5ddbb40cff27dcc92122d7f8b7c8f401048","chainSlug":"arbitrum"},"adapter":"layerzero"}

arbitrum canonical via layerzero 4

0x6f63d5ddbb40cff27dcc92122d7f8b7c8f401048same 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":"HYB","source_tx":null,"message_id":"1391654060855263244","message_ts":"2025-07-07T05:36:23","source_url":"https://layerzeroscan.com/address/0x6f63D5ddbB40Cff27DcC92122D7f8b7C8F401048","message_url":"https://discord.com/channels/1341185540162195456/1341864130071498792/1391654060855263244","source_kind":"oft_address","curator_liquidity":false}
registry	+3	{"tx":"0xc912384ed8e2de68bef1852a71d977829b590215101bc66222c8a01bda257455","from":"bridge_pin"}

binance mint burn potential · no transfer seen 3

0x6f63d5ddbb40cff27dcc92122d7f8b7c8f401048same open

illiquidpools hold $0, under the floor

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

same_address

{"chain":"binance"}

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 arbitrum 1 of 1 reachable

binance layerzero 0xc912384e… 20 h ago

from binance 0 of 1 reachable

No transfer has been seen leaving binance.

show 1 unreachable hide unreachable

arbitrum no transfer seen

Pins behind this token

Pin	Received	Bridge	Bridge tx	Outcome	Discovery took
#9306	20 h ago	layerzeroarbitrum → binance	0xc912384e…257455	DISCOVERED	9 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.