SQD

Subsquid

status: partly reported3/3 checked · 2 liquid · 2 reported · hot
first bridged: 2 d ago
arrived via: portal_bridge
contracts: 5 on 3 chains
confirmed by a transfer: 4 of 5
liquidity: 3 of 3 chains checked · 2 liquid
checking: hot
already alerted on: arbitrum, binance
pins: 1

Lifecycle

first pin received 2026-09-03 06:06:44 UTC · 2 d ago #7985 via portal_bridge
token discovered 2026-09-02 20:13:19 UTC · 2 d ago 5 contracts today
first liquid 2026-09-04 06:31:03 UTC · 19 h ago a chain quoted liquid
first alert 2026-09-04 06:31:03 UTC · 19 h ago multi_chain_liquid, sent 19 h ago
reported chains arbitrum, binance — 2 of 3

Where this token lives

More than one contract on arbitrum (2), 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 via portal_bridge 8

0xe50e3d1a46070444f44df911359033f2937fcc13 open

liquidlast verified 19 h ago

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

registry	+3	{"tx":"0xc298976f1624b08aea77379b796ea478830aff437f54ebce3604d2979b116fb1","from":"bridge_pin"}
derivation	+5	{"via":"origin_from_index","adapter":"portal_bridge","originChainId":4}

arbitrum mint burn via portal_bridge 13

0x1337420ded5adb9980cfc35f8f2b054ea86f8ab1same open

liquidlast verified 19 h ago

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

registry	+3	{"tx":"0x340ad4246be1fb65ae6ec424fcf9f68dee83c0f892a8d77a27cb5cad33c2d694","from":"bridge_pin"}
derivation	+5	{"via":"origin_from_index","adapter":"portal_bridge","originChainId":23}
derivation	+5	{"via":"ntt_peer","adapter":"portal_bridge","manager":"0x37dcb4e443a06a3fe0e7098519c1d81181e5322b","wormholeId":23,"peerManager":"0x37dcb4e443a06a3fe0e7098519c1d81181e5322b"}

binance lock mint wrapper via portal_bridge shadowed · not checked 5

0xaa3e4cfca59a6b11d95d9f11a7783326572fa194 open

liquidlast verified 20 h ago

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

derivation

{"via":"wrappedAsset","adapter":"portal_bridge","tokenBridge":"0xb6f6d86a8f9879a9c87f643768d9efc38c1da6e7","originChainId":23}

arbitrum lock mint wrapper via portal_bridge shadowed · not checked 5

0x4cd70d3a0d4378b340e7081c564febcfa1e8e693 open

liquidlast verified 20 h ago

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

derivation

{"via":"wrappedAsset","adapter":"portal_bridge","tokenBridge":"0x0b2402144bb366a632d14b83f244d2e0e21bd39c","originChainId":4}

ethereum mint burn potential · no transfer seen 3

0x1337420ded5adb9980cfc35f8f2b054ea86f8ab1same 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":"ethereum"}

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

binance portal_bridge 0xf5bcf61d… 32 h ago

show 1 unreachable hide unreachable

ethereum no transfer seen

from binance 1 of 2 reachable

arbitrum portal_bridge 0x0e6470b7… 32 h ago

show 1 unreachable hide unreachable

ethereum no transfer seen

from ethereum 0 of 2 reachable

No transfer has been seen leaving ethereum.

show 2 unreachable hide unreachable

arbitrum no transfer seen

binance no transfer seen

Pins behind this token

Pin	Received	Bridge	Bridge tx	Outcome	Discovery took
#7985	2 d ago	portal_bridgebinance → arbitrum	0xc298976f…116fb1	DISCOVERED	11 h

Alerts

Kind	Created	State	Sent	Telegram id
multi_chain_liquid	19 h ago	SENT	19 h ago	643

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