YLDS (YLDS)

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

Asset

YLDS (YLDS)

Type

token

Available networks

1

Native networks

Contract token

Route support

Not currently available

What you need to know

What YLDS represents

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

YLDS contract-token identity

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

YLDS network-by-network inventory

Provenance (contract)

Receiving YLDS without a network mismatch

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

YLDS route-support boundary

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

YLDS 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

YLDS (YLDS) FAQs

Which contracts identify YLDS?

YLDS is contract-based on Provenance. Use the exact route representation rather than the ticker alone.

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

Which receiving networks are recorded for YLDS?

Provenance

Can I use a live YLDS route now?

Sasquatch does not currently list a transaction route for YLDS.

What is the safest YLDS receiving check?

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

View all Help Center FAQs →