edgeX (EDGE)

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

Asset

edgeX (EDGE)

Type

token

Available networks

1

Native networks

Contract token

Route support

Not currently available

What you need to know

What EDGE represents

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

EDGE contract-token identity

edgeX 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.

EDGE network-by-network inventory

Ethereum (contract)

Receiving EDGE without a network mismatch

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

EDGE route-support boundary

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

EDGE 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

edgeX (EDGE) FAQs

Which contracts identify EDGE?

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

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

Which receiving networks are recorded for EDGE?

Ethereum

Can I use a live EDGE route now?

Sasquatch does not currently list a transaction route for edgeX.

What is the safest EDGE receiving check?

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

View all Help Center FAQs →