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