MetaDAO (META)

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

Asset

MetaDAO (META)

Type

token

Available networks

1

Native networks

Contract token

Route support

Not currently available

What you need to know

What META represents

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

META contract-token identity

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

META network-by-network inventory

Solana (contract)

Receiving META without a network mismatch

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

META route-support boundary

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

META 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

MetaDAO (META) FAQs

Which contracts identify META?

META is contract-based on Solana. Use the exact route representation rather than the ticker alone.

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

Which receiving networks are recorded for META?

Solana

Can I use a live META route now?

Sasquatch does not currently list a transaction route for MetaDAO.

What is the safest META receiving check?

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

View all Help Center FAQs →