PIEVERSE

Pieverse 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: 2

Lifecycle

first pin received 2026-09-03 06:06:13 UTC · 2 d ago #6326 via layerzero
token discovered 2026-09-03 07:05:32 UTC · 2 d ago 2 contracts today
first liquid 2026-09-05 04:30:21 UTC · 2 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

0x0e63b9c287e32a05e6b9ab8ee8df88a2760225a9same open

illiquidtradeable but costly — 1038 bps · 10.38%

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

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

binance canonical via layerzero 3

0x0e63b9c287e32a05e6b9ab8ee8df88a2760225a9same open

liquid9 bps · 0.09% via kyberswap

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

registry

{"tx":"0x91bac4923b26f666c8c3f13d614f5353ec4921817c2e5dcff4657475d878726d","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 0x91bac492… 2 d ago

from ethereum 1 of 1 reachable

binance layerzero 0x4b8e2ced… 2 d ago

Pins behind this token

Pin	Received	Bridge	Bridge tx	Outcome	Discovery took
#7231	2 d ago	layerzeroethereum → binance	0x06fedab2…4c41c3	SKIPPED_DUPLICATE	9 h
#6326	2 d ago	layerzerobinance → ethereum	0x91bac492…78726d	DISCOVERED	59 min

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