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