binance
canonical · via layerzero
confirmed
added
0x0e63b9c2…0225a9same
open
liquidlast verified 2 mo ago3
Bridge registry lists itstrong +3
PI
2 contracts on 2 chains · 2 routes via LZLayerZero
PIEVERSE Pieverse Token✓ added by tokens.json
2 contracts on 2 chains · 2 routes via LZLayerZero- status
- added2 of 2 chains · 2 reported · hot
- first bridged
- 2 mo ago2026-09-03 07:05
- confirmed by a transfer
- 2 of 2every contract seen in a tx
- already alerted
- binance, ethereum1 alerts
- pins
- 2latest 2 mo ago
possible twin of PIEVERSE #2242
Contracts
binance
canonical · via layerzero
confirmed
added
ethereum
mint burn · via layerzero
confirmed
added
0x0e63b9c2…0225a9same
open
liquidlast verified 2 mo ago8
Same address as on another chainweak +3
Peer map: the protocol names this contract as a peerstrong +5
…
Routes
2 confirmed · 0 possible| Lane | Bridge | Evidence | Proof | Last seen |
|---|---|---|---|---|
ethereum 0x0e63b9c2…0225a9 → binance 0x0e63b9c2…0225a9 |
LZLayerZero | confirmed | 0x4b8e2ced…03c569 | 2 mo ago |
binance 0x0e63b9c2…0225a9 → ethereum 0x0e63b9c2…0225a9 |
LZLayerZero | confirmed | 0x91bac492…78726d | 2 mo ago |
How it moves
transfer seen (moving)peer map onlyring = liquidity on that chain
Add another bridge transaction. Every transfer you paste re-checks the contracts on both ends and adds the route it proves.
Lifecycle
Token discovered
2026-09-03 07:05 UTC · 2 mo ago · 2 contracts today
First pin received
2026-09-03 06:06 UTC · 2 mo ago · #6326 via layerzero
First liquid
2026-09-07 02:38 UTC · 2 mo ago · a chain quoted liquid
First alert
2026-09-07 02:38 UTC · 2 mo ago · multi_chain_liquid, sent 2 mo ago
All chains reported
binance, ethereum — 2 of 2
history · 1 alerts · 0 merges · 0 detached
Alerts
| Kind | Created | State | Sent | Rechecks | Outcome | Telegram |
|---|---|---|---|---|---|---|
| multi_chain_liquid | 2 mo ago | SENT | 2 mo ago | 0 | — | 1775 |