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