SDM
Shieldeum
status fully reported 2/2 checked · 2 liquid · 2 reported · hot
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 · 2 liquid
checking hot
already alerted on base, binance
pins 0
Lifecycle
first pin received
pending
no pin linked (added by hand, or before pins were tracked)
token discovered
2026-09-02 22:11:16 UTC · 2 d ago
2 contracts today
first liquid
2026-09-04 05:57:40 UTC · 19 h ago
a chain quoted liquid
first alert
2026-09-04 05:57:40 UTC · 19 h ago
multi_chain_liquid, sent 19 h ago
reported chains
base, binance — 2 of 2
Where this token lives
base
mint burn
via layerzero
5
0x9cfe02eb040c6f5718126128dbba0c1d364d9c07
copy
open
liquid last verified 19 h ago
Every source here is an inference. A contract on this chain has not confirmed the link itself.
bridge_transfer +5 {"tx":"0x335e3fa237dbaae97725c440d27cf590824ff4edee6ec7bfafac5b0909c31fb6","adapter":"layerzero"}
binance
canonical
via layerzero
3
0x516f8a1fb458ebdcfd0f544ff85c69c1c0ebc31d
copy
open
liquid last verified 19 h ago
1 of 1 sources are protocol-attested — a contract confirmed this link.
registry +3 {"tx":"0x335e3fa237dbaae97725c440d27cf590824ff4edee6ec7bfafac5b0909c31fb6","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 base
1 of 1 reachable
from binance
1 of 1 reachable
Alerts
Kind Created State Sent Telegram id
multi_chain_liquid 19 h ago
SENT
19 h ago 520