What CUSD represents
Cap USD (CUSD) is available in network-specific native or token forms. Cap USD belongs to the token category and must be verified through its network-specific native label or contract representation.
Cap USD (CUSD)
Review CUSD network versions, native and token forms, receiving considerations, and currently available Sasquatch routes.
Asset
Cap USD (CUSD)
Type
token
Available networks
2
Native networks
Contract token
Route support
Not currently available
What you need to know
CUSD contract-token identity
Cap USD belongs to the token category and must be verified through its network-specific native label or contract representation. Recorded contract networks include Ethereum, MegaETH; network gas remains a separate native balance.
CUSD network-by-network inventory
Ethereum (contract), MegaETH (contract)
Receiving CUSD without a network mismatch
Confirm the CUSD network, contract or native label, and receiving address before using a route. Do not identify CUSD solely by ticker; verify the asset and network representation. CUSD can use different contracts on different networks.
CUSD route-support boundary
Sasquatch does not currently list a transaction route for Cap USD. Asset metadata is not proof of a live provider route.
CUSD 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 USD (CUSD) FAQs
Which contracts identify CUSD?
CUSD is contract-based on Ethereum, MegaETH. Use the exact route representation rather than the ticker alone.
Does CUSD 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 CUSD.
Which receiving networks are recorded for CUSD?
Ethereum, MegaETH
Can I use a live CUSD route now?
Sasquatch does not currently list a transaction route for Cap USD.
What is the safest CUSD receiving check?
Confirm the CUSD network, contract or native label, and receiving address before using a route. Do not identify CUSD solely by ticker; verify the asset and network representation.