What JUP represents
Jupiter (JUP) is available in network-specific native or token forms. Jupiter belongs to the token category and must be verified through its network-specific native label or contract representation.
Jupiter (JUP)
Review JUP network versions, native and token forms, receiving considerations, and currently available Sasquatch routes.
Asset
Jupiter (JUP)
Type
token
Available networks
2
Native networks
Contract token
Route support
Not currently available
What you need to know
JUP contract-token identity
Jupiter belongs to the token category and must be verified through its network-specific native label or contract representation. Recorded contract networks include Solana, Unichain; network gas remains a separate native balance.
JUP network-by-network inventory
Solana (contract), Unichain (contract)
Receiving JUP without a network mismatch
Confirm the JUP network, contract or native label, and receiving address before using a route. Do not identify JUP solely by ticker; verify the asset and network representation. JUP can use different contracts on different networks.
JUP route-support boundary
Sasquatch does not currently list a transaction route for Jupiter. Asset metadata is not proof of a live provider route.
JUP 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
Jupiter (JUP) FAQs
Which contracts identify JUP?
JUP is contract-based on Solana, Unichain. Use the exact route representation rather than the ticker alone.
Does JUP 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 JUP.
Which receiving networks are recorded for JUP?
Solana, Unichain
Can I use a live JUP route now?
Sasquatch does not currently list a transaction route for Jupiter.
What is the safest JUP receiving check?
Confirm the JUP network, contract or native label, and receiving address before using a route. Do not identify JUP solely by ticker; verify the asset and network representation.