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