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