HAI

HAI-OFT

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

Lifecycle

first pin received 2026-09-03 06:06:41 UTC · 2 d ago #7597 via layerzero
token discovered 2026-09-03 16:25:37 UTC · 2 d ago 4 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 canonical potential · no transfer seen 1

0x6403af1267cacc0714c1bd916b12f80e179c0558same 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":["no test Txn. for now"],"proven":false,"ticker":"HAI","source_tx":null,"message_id":"1395856059112886353","message_ts":"2025-07-18T19:53:38","source_url":null,"message_url":"https://discord.com/channels/1341185540162195456/1341864130071498792/1395856059112886353","source_kind":"none","curator_liquidity":false}

ethereum mint burn via layerzero 6

0x6403af1267cacc0714c1bd916b12f80e179c0558same open

illiquidpools hold $0, under the floor

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

peer_map	+5	{"via":{"address":"0x7002987e5f63716273e77b51e12a578143c222aa","chainSlug":"base"},"adapter":"layerzero"}
discord	+1	{"notes":["no test Txn. for now"],"proven":false,"ticker":"HAI","source_tx":null,"message_id":"1395856059112886353","message_ts":"2025-07-18T19:53:38","source_url":null,"message_url":"https://discord.com/channels/1341185540162195456/1341864130071498792/1395856059112886353","source_kind":"none","curator_liquidity":false}

binance mint burn via layerzero shadowed · not checked 5

0x582a560b9f8eaa5b6c889d7674532bcd61f066ec open

illiquidpools hold $0, under the floor

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

peer_map

{"via":{"address":"0x7002987e5f63716273e77b51e12a578143c222aa","chainSlug":"base"},"adapter":"layerzero"}

base canonical via layerzero 4

0x7002987e5f63716273e77b51e12a578143c222aa open

illiquidpools hold $0, under the floor

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

registry	+3	{"tx":"0x75718d51b3b31a0301adc3441effc2dbf56e5aa59be16daa057ec7c14458349b","from":"bridge_pin"}
discord	+1	{"notes":["no test Txn. for now"],"proven":false,"ticker":"HAI","source_tx":null,"message_id":"1395856059112886353","message_ts":"2025-07-18T19:53:38","source_url":null,"message_url":"https://discord.com/channels/1341185540162195456/1341864130071498792/1395856059112886353","source_kind":"none","curator_liquidity":true}

How it moves between chains

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 2 of 2 reachable

binance layerzero 0xeb743685… 2 d ago

ethereum layerzero 0x75718d51… 2 d ago

from binance 1 of 2 reachable

base layerzero 0xfcf360b8… 2 d ago

show 1 unreachable hide unreachable

ethereum no transfer seen

from ethereum 2 of 2 reachable

base layerzero 0xabd202ec… 2 d ago

binance layerzero 0xacaf1d6d… 2 d ago

Pins behind this token

Pin	Received	Bridge	Bridge tx	Outcome	Discovery took
#7597	2 d ago	layerzerobase → ethereum	0x75718d51…58349b	DISCOVERED	10 h

Every address above came from an on-chain read. The evidence trail shows which read produced it.