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