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.
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
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 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.
Ethereum (contract), BNB Chain (contract)
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.
Sasquatch does not currently list a transaction route for Cap. Asset metadata is not proof of a live provider route.
Approvals, token transfers, wallet reuse, amounts, timing, and later consolidation can remain visible. Private Route availability and identity requirements must be checked separately.
CAP is contract-based on Ethereum, BNB Chain. Use the exact route representation rather than the ticker alone.
No native origin is recorded in this registry. Network gas is paid with each chain's native asset, not automatically with CAP.
Ethereum, BNB Chain
Sasquatch does not currently list a transaction route for Cap.
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.