# Supported Collateral

Our vision is for $USC to be an overcollateralized stablecoin backed by multiple collateral types. At launch, CDCETH was the first collateral to be supported. We’ve since expanded support to include cdcBTC and LCRO, offering users greater flexibility and utility. Orby now supports **CRO as a collateral option** for the LCRO Shuttle.<br>

CDCETH is a type of receipt token representing staked Ether (ETH) and any accrued staking rewards. Read more about the token [here](https://crypto.com/document/cdceth_whitepaper).<br>

CDCBTC is a token backed 1:1 by native Bitcoin (BTC), with the underlying BTC securely held in cold storage under Crypto.com’s custody. Read the whitepaper [here](https://crypto.com/document/cdcbtc-whitepaper.pdf).<br>

LCRO is a liquid staking token that represents staked CRO through Veno. It is a yield-bearing, auto-compounding asset, allowing users to passively earn staking rewards. Read more [here](https://crypto.com/en/product-news/crypto-com-app-lists-liquid-cro-lcro).

CRO is the native token of the Cronos chain. Read more [here](https://crypto.com/price/cronos). In order to use CRO as collateral, you will need to do the following:

* Open a new LCRO Shuttle using **CRO as collateral**
* Add **CRO** to LCRO Shuttle
* Withdraw collateral in **CRO** instead of LCRO
* Repay full debt and receive **CRO** back into their wallet

Orby handles the swap between **CRO ⇄ LCRO** in the background via Ferro or VVS, using the most efficient route based on price, slippage, and swap fees.

<br>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://doc.orby.network/overview/supported-collateral.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.