What CRO represents
Cronos (CRO) is available in network-specific native or token forms. Cronos belongs to the token category and must be verified through its network-specific native label or contract representation.
Review CRO network versions, native and token forms, receiving considerations, and currently available Sasquatch routes.
Asset
Cronos (CRO)
Type
Native asset
Available networks
2
Native networks
Cronos
Route support
Not currently available
Cronos (CRO) is available in network-specific native or token forms. Cronos belongs to the token category and must be verified through its network-specific native label or contract representation.
CRO is recorded as native on Cronos. Native status describes the ledger balance and gas behavior on that network, not every token carrying the ticker.
Contract forms are recorded on Ethereum. Each form needs its own address, wallet, and network check.
Ethereum (contract), Cronos (native)
The contract representations currently share one recorded decimal format, but contract identity and network still require independent verification.
Confirm the CRO network, contract or native label, and receiving address before using a route. Do not identify CRO solely by ticker; verify the asset and network representation. Native CRO and token representations on other networks are not interchangeable.
Sasquatch does not currently list a transaction route for Cronos. 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.
CRO is recorded as native on Cronos. Other listed forms can be contract or provider-mapped representations.
No. Native status belongs to the recorded origin network; another chain's CRO-labelled token maintains separate balances and transaction history.
Ethereum, Cronos
Sasquatch does not currently list a transaction route for Cronos.
Confirm the CRO network, contract or native label, and receiving address before using a route. Do not identify CRO solely by ticker; verify the asset and network representation.