PAL
Paladin Token
status illiquid 2/2 checked · 0 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 · 0 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-03 00:20:26 UTC · 2 d ago
2 contracts today
first liquid
pending
not yet
first alert
pending
not yet
reported chains
pending
none yet
Where this token lives
sonic
mint burn
via layerzero
5
0xe4a4353cd8f008f1a70f1a564535990479e8ceb7
copy
open
illiquid pools hold $0, under the floor
Every source here is an inference. A contract on this chain has not confirmed the link itself.
bridge_transfer +5 {"tx":"0xe9b7adf8e18ab51299fc201a1055d93fe77dd9384c307dcc7836836293ed355a","adapter":"layerzero"}
ethereum
canonical
via layerzero
3
0xab846fb6c81370327e784ae7cbb6d6a6af6ff4bf
copy
open
illiquid pools hold $0, under the floor
1 of 1 sources are protocol-attested — a contract confirmed this link.
registry +3 {"tx":"0xe9b7adf8e18ab51299fc201a1055d93fe77dd9384c307dcc7836836293ed355a","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 ethereum
1 of 1 reachable
from sonic
1 of 1 reachable