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