0x Protocol (ZRX)

Review ZRX network versions, native and token forms, receiving considerations, and currently available Sasquatch routes.

Asset

0x Protocol (ZRX)

Type

token

Available networks

1

Native networks

Contract token

Route support

Not currently available

What you need to know

What ZRX represents

0x Protocol (ZRX) is available in network-specific native or token forms. 0x Protocol belongs to the token category and must be verified through its network-specific native label or contract representation.

ZRX contract-token identity

0x Protocol belongs to the token category and must be verified through its network-specific native label or contract representation. Recorded contract networks include Ethereum; network gas remains a separate native balance.

ZRX network-by-network inventory

Ethereum (contract)

Receiving ZRX without a network mismatch

Confirm the ZRX network, contract or native label, and receiving address before using a route. Do not identify ZRX solely by ticker; verify the asset and network representation. ZRX can use different contracts on different networks.

ZRX route-support boundary

Sasquatch does not currently list a transaction route for 0x Protocol. Asset metadata is not proof of a live provider route.

ZRX 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

0x Protocol (ZRX) FAQs

Which contracts identify ZRX?

ZRX is contract-based on Ethereum. Use the exact route representation rather than the ticker alone.

Does ZRX 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 ZRX.

Which receiving networks are recorded for ZRX?

Ethereum

Can I use a live ZRX route now?

Sasquatch does not currently list a transaction route for 0x Protocol.

What is the safest ZRX receiving check?

Confirm the ZRX network, contract or native label, and receiving address before using a route. Do not identify ZRX solely by ticker; verify the asset and network representation.

View all Help Center FAQs →