SAS
ShibArmyStrong
status illiquid 3/3 checked · 0 liquid · warm
first bridged 2 d ago
arrived via ccip
contracts 3 on 3 chains
confirmed by a transfer 3 of 3
liquidity 3 of 3 chains checked · 0 liquid
checking warm
already alerted on nothing yet
Lifecycle
first pin received
2026-09-03 06:06:40 UTC · 2 d ago
#7338 via ccip
token discovered
2026-09-03 15:39:37 UTC · 2 d ago
3 contracts today
first liquid
pending
not yet
first alert
pending
not yet
reported chains
pending
none yet
Where this token lives
base
canonical
via ccip
3
0x28be7e8cd8125cb7a74d2002a5862e1bfd774cd9same
copy
open
illiquid pools hold $0, under the floor
1 of 1 sources are protocol-attested — a contract confirmed this link.
registry +3 {"tx":"0xc3ef10c169d146aa87d3a5697dd3a2e9db5eeee861d415bdf84fbf878b23ce2c","from":"bridge_pin"}
ethereum
mint burn
3
0x28be7e8cd8125cb7a74d2002a5862e1bfd774cd9same
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.
same_address +3 {"chain":"ethereum"}
binance
mint burn
3
0x28be7e8cd8125cb7a74d2002a5862e1bfd774cd9same
copy
open
illiquid tradeable but costly — 613 bps · 6.13%
Every source here is an inference. A contract on this chain has not confirmed the link itself.
same_address +3 {"chain":"binance"}
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 2 reachable
show 1 unreachable
hide unreachable
→
ethereum
no transfer seen
from binance
0 of 2 reachable
No transfer has been seen leaving binance.
show 2 unreachable
hide unreachable
→
base
no transfer seen
→
ethereum
no transfer seen
from ethereum
2 of 2 reachable
Pins behind this token