SKAI

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

Lifecycle

first pin received 2026-09-03 06:06:44 UTC · 2 d ago #7916 via base_bridge
token discovered 2026-09-03 01:38:30 UTC · 2 d ago 2 contracts today
first liquid 2026-09-03 02:15:36 UTC · 2 d ago a chain quoted liquid
first alert 2026-09-03 02:15:36 UTC · 2 d ago multi_chain_liquid, sent 2 d ago
reported chains base, ethereum — 2 of 2

Where this token lives

base mint burn via base_bridge 8

0xe7399151b688a265f347693d358821a5a8c213ec open

liquidlast verified 2 d ago

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

registry	+3	{"tx":"0x8379f616bcc17f49b4f7423e3a205a72c8c83ef2270f0ad88f23983f083ee0de","from":"bridge_pin"}
derivation	+5	{"via":"remoteToken","adapter":"base_bridge"}

ethereum canonical via base_bridge 5

0xcf078da6e85389de507ceede0e3d217e457b9d49 open

liquidlast verified 2 d ago

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

derivation

{"via":"remoteToken","adapter":"base_bridge","l2Chain":"base","l2Token":"0xe7399151b688a265f347693d358821a5a8c213ec"}

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

ethereum base_bridge 0x8379f616… 2 d ago

from ethereum 1 of 1 reachable

base base_bridge 0xe86fa5a5… 36 h ago

Pins behind this token

Pin	Received	Bridge	Bridge tx	Outcome	Discovery took
#7916	2 d ago	base_bridgeethereum → base	0x0ba26433…d9fe0f	SKIPPED_DUPLICATE	10 h

Alerts

Kind	Created	State	Sent	Telegram id
multi_chain_liquid	2 d ago	SENT	2 d ago	86

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