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