> For the complete documentation index, see [llms.txt](https://udonfi-1.gitbook.io/udonfi-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://udonfi-1.gitbook.io/udonfi-docs/liquid-staking/udon-liquid-staking-stchr.md).

# Udon Liquid Staking (stCHR)

### [Direct link to heading](broken://pages/f6ecdaef51e74b4e2fcf91e934f7f2c23e9013fc) What is Udon Liquid Staking?

<details>

<summary>Answer</summary>

Udon introduces **Liquid Staking** to the Chromia ecosystem — a new way to stake CHR and earn validator rewards while keeping your tokens liquid.\
When you stake CHR through Udon, you receive **stCHR**, a token that represents your staked CHR and the rewards it generates.

Instead of locking your CHR in Chromia’s Vault, you stay flexible — your stCHR can be used in DeFi, traded, or supplied in Udon for additional yield.

</details>

***

### [Direct link to heading](broken://pages/adf827c1b038c2340911369435094fb85e37fd35) What is stCHR?

<details>

<summary>Answer</summary>

**stCHR** is the **Liquid Staking Token (LST)** of **CHR**, created by Udon.\
It represents your staked CHR on the Chromia mainnet and its accumulated staking rewards. Over time, the value of each stCHR increases relative to CHR as validator rewards are distributed.

</details>

***

#### [Direct link to heading](broken://pages/a41157bd0681320afb1c6726597da44f1138cd74) Why use Liquid Staking?

| Method          |                                               Platform | Token Received | Liquidity | Unstaking Time |
| --------------- | -----------------------------------------------------: | -------------- | :-------: | -------------: |
| Regular Staking | [Chromia Vault](https://vault.chromia.com/en/staking/) | CHR (locked)   |    ❌ No   |        14 days |
| Liquid Staking  |                  [Udon.fi](https://udonfi.xyz/staking) | stCHR (liquid) |   ✅ Yes   |        14 days |

With Udon, you don’t just stake — you **earn more**:

{% stepper %}
{% step %}

### Stake CHR → Receive stCHR

Stake your CHR through Udon and receive stCHR in return, which represents your staked position and accruing rewards.
{% endstep %}

{% step %}

### Supply stCHR → Earn extra APR

Supply your stCHR in Udon’s DeFi markets to earn additional APR on top of staking rewards.
{% endstep %}

{% step %}

### Claim rewards daily → Boost your yield

Rewards are claimable daily, allowing you to compound or re-deploy for higher yield.
{% endstep %}

{% step %}

### Redeem stCHR → Get back CHR after 14 days

When you redeem stCHR, you receive CHR back after the 14-day unstaking period.
{% endstep %}
{% endstepper %}

***

#### [Direct link to heading](broken://pages/67394940c7e37afdfc5756d9f919bd3ee910c195) Key Benefits

* Earn validator rewards from Chromia
* Keep your asset liquid with stCHR
* Boost APR with Udon’s DeFi incentives
* Simple, transparent, and user-friendly

> **Udon turns your CHR into a productive, flexible asset.**


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://udonfi-1.gitbook.io/udonfi-docs/liquid-staking/udon-liquid-staking-stchr.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.