> For the complete documentation index, see [llms.txt](https://docs.orchai.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.orchai.io/orchai-liquid-staking/overview.md). # Overview Stake ORAI without locking it up. Earn and freely use it within DeFi ## What is Orchai Liquid Staking Orchai Liquid Staking is a liquid staking protocol built on Oraichain. It tokenizes staked ORAI and allows users to use it within Decentralized Finance dApps freely. ## Why Liquid Staking Oraichain is a Proof-of-Stake (POS) network that generates returns for users who [delegate](https://docs.orai.io/developers/guide/delegate-tokens-to-a-validator) the ORAI token on validator nodes to secure the network. To do this, users are required to lock up the ORAI token for a predetermined time. This results in the lock up of capital, unable to be utilized within Decentralized Finance (DeFi). Liquid Staking provides a solution for freeing up this locked up capital, creating greater capital efficiency within the Oraichain network. By tokenizing the staked ORAI into **sORAI** or **scORAI**, users will now be able to utilize the asset within Decentralized Finance dApps while earning passive returns from Oraichain staking itself. The sORAI and scORAI assets provide developers and users with a wealth of strategies and options to build off of. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.orchai.io/orchai-liquid-staking/overview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.