Cap (CAP)

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

Asset

Cap (CAP)

Type

token

Available networks

2

Native networks

Contract token

Route support

Not currently available

What you need to know

What CAP represents

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

CAP contract-token identity

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

CAP network-by-network inventory

Ethereum (contract), BNB Chain (contract)

Receiving CAP without a network mismatch

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

CAP route-support boundary

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

CAP 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

Cap (CAP) FAQs

Which contracts identify CAP?

CAP is contract-based on Ethereum, BNB Chain. Use the exact route representation rather than the ticker alone.

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

Which receiving networks are recorded for CAP?

Ethereum, BNB Chain

Can I use a live CAP route now?

Sasquatch does not currently list a transaction route for Cap.

What is the safest CAP receiving check?

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

View all Help Center FAQs →