JOE
JoeToken
status liquid 4/4 checked · 1 liquid · warm
first bridged 2 d ago
arrived via layerzero
contracts 4 on 4 chains
confirmed by a transfer 3 of 4
liquidity 4 of 4 chains checked · 1 liquid
checking warm
already alerted on nothing yet
pins 0
Lifecycle
first pin received
pending
no pin linked (added by hand, or before pins were tracked)
token discovered
2026-09-02 21:39:47 UTC · 2 d ago
4 contracts today
first liquid
2026-09-05 03:41:30 UTC · 8 min ago
a chain quoted liquid
first alert
pending
not yet
reported chains
pending
none yet
Where this token lives
binance
mint burn
via layerzero
10
0x371c7ec6d8039ff7933a2aa28eb827ffe1f52f07same
copy
open
illiquid loses 2467 bps · 24.67% round-trip
1 of 3 sources are protocol-attested — a contract confirmed this link.
same_address +3 {"chain":"binance"} codehash +2 {"codehash":"0xcf40b0f5ffe08b432d5fff6db8b4c7fda6e59fa24860b2ea429d9944e6d08a20"} peer_map +5 {"via":{"address":"0x371c7ec6d8039ff7933a2aa28eb827ffe1f52f07","chainSlug":"arbitrum"},"adapter":"layerzero"}
ethereum
mint burn
via layerzero
potential · no transfer seen
8
0x371c7ec6d8039ff7933a2aa28eb827ffe1f52f07same
copy
open
illiquid pools hold $0, 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":"0x371c7ec6d8039ff7933a2aa28eb827ffe1f52f07","chainSlug":"arbitrum"},"adapter":"layerzero"}
avalanche
canonical
via layerzero
5
0x6e84a6216ea6dacc71ee8e6b0a5b7322eebc0fdd
copy
open
liquid 46 bps · 0.46% via kyberswap
1 of 1 sources are protocol-attested — a contract confirmed this link.
peer_map +5 {"via":{"address":"0x371c7ec6d8039ff7933a2aa28eb827ffe1f52f07","chainSlug":"arbitrum"},"adapter":"layerzero","oftAdapter":"0x371c7ec6d8039ff7933a2aa28eb827ffe1f52f07","unwrappedTo":"0x6e84a6216ea6dacc71ee8e6b0a5b7322eebc0fdd"}
arbitrum
canonical
via layerzero
3
0x371c7ec6d8039ff7933a2aa28eb827ffe1f52f07same
copy
open
illiquid tradeable but costly — 797 bps · 7.97%
1 of 1 sources are protocol-attested — a contract confirmed this link.
registry +3 {"tx":"0x9f6b18c92d1033e6022ec42252a92687d53c5c8266362579bef72be3d9881f10","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 arbitrum
2 of 3 reachable
show 1 unreachable
hide unreachable
→
ethereum
no transfer seen
from avalanche
2 of 3 reachable
show 1 unreachable
hide unreachable
→
ethereum
no transfer seen
from binance
2 of 3 reachable
show 1 unreachable
hide unreachable
→
ethereum
no transfer seen
from ethereum
0 of 3 reachable
No transfer has been seen leaving ethereum.
show 3 unreachable
hide unreachable
→
arbitrum
no transfer seen
→
avalanche
no transfer seen
→
binance
no transfer seen