SHELL

MyShell Token

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

Lifecycle

first pin received 2026-09-03 06:06:44 UTC · 2 d ago #8031 via layerzero
token discovered 2026-09-03 01:41:02 UTC · 2 d ago 2 contracts today
first liquid 2026-09-05 06:48:18 UTC · 10 min ago a chain quoted liquid
first alert pending not yet
reported chains pending none yet

Where this token lives

ethereum mint burn via layerzero 8

0xf2c88757f8d03634671208935974b60a2a28bdb3same open

illiquidpools hold $4, under the floor

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

same_address	+3	{"chain":"ethereum"}
peer_map	+5	{"via":{"address":"0xf2c88757f8d03634671208935974b60a2a28bdb3","chainSlug":"binance"},"adapter":"layerzero"}

binance canonical via layerzero 3

0xf2c88757f8d03634671208935974b60a2a28bdb3same open

liquid201 bps · 2.01% via kyberswap

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

registry

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

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 0x1bd5d06c… 2 d ago

from ethereum 1 of 1 reachable

binance layerzero 0x05f6834d… 2 d ago

Pins behind this token

Pin	Received	Bridge	Bridge tx	Outcome	Discovery took
#8031	2 d ago	layerzeroethereum → binance	0x10caba2a…b81cf1	SKIPPED_DUPLICATE	11 h

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