Quant (QNT)

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

Asset

Quant (QNT)

Type

token

Available networks

2

Native networks

Contract token

Route support

Not currently available

What you need to know

What QNT represents

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

QNT contract-token identity

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

QNT network-by-network inventory

Ethereum (contract), Energi (contract)

Receiving QNT without a network mismatch

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

QNT route-support boundary

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

QNT 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

Quant (QNT) FAQs

Which contracts identify QNT?

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

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

Which receiving networks are recorded for QNT?

Ethereum, Energi

Can I use a live QNT route now?

Sasquatch does not currently list a transaction route for Quant.

What is the safest QNT receiving check?

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

View all Help Center FAQs →