What JST represents
JUST (JST) is available in network-specific native or token forms. JUST belongs to the token category and must be verified through its network-specific native label or contract representation.
JUST (JST)
Review JST network versions, native and token forms, receiving considerations, and currently available Sasquatch routes.
Asset
JUST (JST)
Type
token
Available networks
0
Native networks
Contract token
Route support
Not currently available
What you need to know
JST contract-token identity
JUST belongs to the token category and must be verified through its network-specific native label or contract representation. Recorded contract networks include the networks listed below; network gas remains a separate native balance.
JST network-by-network inventory
No network representation is currently listed.
Receiving JST without a network mismatch
Confirm the JST network, contract or native label, and receiving address before using a route. Do not identify JST solely by ticker; verify the asset and network representation. JST can use different contracts on different networks.
JST route-support boundary
Sasquatch does not currently list a transaction route for JUST. Asset metadata is not proof of a live provider route.
JST privacy and wallet linking
Approvals, token transfers, wallet reuse, amounts, timing, and later consolidation can remain visible. Private Route availability and identity requirements must be checked separately.
Related routes
JUST (JST) FAQs
Which contracts identify JST?
JST is contract-based on the listed networks. Use the exact route representation rather than the ticker alone.
Does JST have a native gas balance?
No native origin is recorded in this registry. Network gas is paid with each chain's native asset, not automatically with JST.
Which receiving networks are recorded for JST?
No network representation is currently listed.
Can I use a live JST route now?
Sasquatch does not currently list a transaction route for JUST.
What is the safest JST receiving check?
Confirm the JST network, contract or native label, and receiving address before using a route. Do not identify JST solely by ticker; verify the asset and network representation.