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