DOS

DAPPOS

status: fully reported2/2 checked · 2 liquid · 2 reported · hot
first bridged: 2 d ago
arrived via: layerzero
contracts: 3 on 2 chains
confirmed by a transfer: 3 of 3
liquidity: 2 of 2 chains checked · 2 liquid
checking: hot
already alerted on: binance, ethereum
pins: 8

Lifecycle

first pin received 2026-09-02 22:59:09 UTC · 2 d ago #3550 via layerzero
token discovered 2026-09-03 03:55:59 UTC · 2 d ago 3 contracts today
first liquid 2026-09-04 06:48:02 UTC · 22 h ago a chain quoted liquid
first alert 2026-09-04 06:48:02 UTC · 22 h ago multi_chain_liquid, sent 22 h ago
reported chains binance, ethereum — 2 of 2

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 5

0xb0f09ea9ae0515c3551080d4a745c8115aa30e37 open

liquidlast verified 22 h ago

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

bridge_transfer

{"tx":"0x9c952003d716eec1fb4896f7f347602af2326f967d5425d565192fc3401a1f2c","adapter":"layerzero"}

ethereum canonical via layerzero 3

0x951f086a127e280724fd93ccc543f65065afeb5esame open

liquidlast verified 22 h ago

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

registry

{"tx":"0x9c952003d716eec1fb4896f7f347602af2326f967d5425d565192fc3401a1f2c","from":"bridge_pin"}

binance mint burn shadowed · not checked 3

0x951f086a127e280724fd93ccc543f65065afeb5esame open

liquidlast verified 26 h ago

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

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

ethereum layerzero 0x3fea3a1d… 32 h ago

from ethereum 1 of 1 reachable

binance layerzero 0x9c952003… 2 d ago

Pins behind this token

Pin	Received	Bridge	Bridge tx	Outcome	Discovery took
#8854	2 d ago	layerzerobinance → ethereum	0xb4801b94…b69c99	SKIPPED_DUPLICATE	15 h
#8789	2 d ago	layerzeroethereum → binance	0xc31797d5…a3ef38	SKIPPED_DUPLICATE	15 h
#5234	2 d ago	layerzeroethereum → binance	0x1258c20b…002538	SKIPPED_DUPLICATE	2 h 49 min
#5171	2 d ago	layerzerobinance → ethereum	0x9987ee6c…af7734	SKIPPED_DUPLICATE	2 h 48 min
#5170	2 d ago	layerzerobinance → ethereum	0xc67f1db1…f1f142	SKIPPED_DUPLICATE	2 h 48 min
#5169	2 d ago	layerzerobinance → ethereum	0x3fea3a1d…cc12ba	SKIPPED_DUPLICATE	2 h 48 min
#5155	2 d ago	layerzeroethereum → binance	0xfcab7344…9b165b	SKIPPED_DUPLICATE	2 h 48 min
#3550	2 d ago	layerzeroethereum → binance	0xfe9a22f0…f9ad69	SKIPPED_DUPLICATE	5 h 31 min

Alerts

Kind	Created	State	Sent	Telegram id
multi_chain_liquid	22 h ago	SENT	22 h ago	699

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