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