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

# What is Liquid Staking

### **The Problem**

Traditionally, staking in Proof-of-Stake (PoS) based chains involves locking token for an extended period of time to receive staking rewards in return. While this process guarantees bond-like returns for stakers, it prevents them from other profitable DeFi opportunities like lending, investing or margin trading on exchanges.

Staking on PoS protocols also requires stakers to either run their own validator, which involves significant friction, or delegate this responsibility to other validators.

### The Solution

Liquid staking protocols issue Liquid Staked Tokens (LSTs) that represent the native token staked on that protocol. This allows stakers to earn staking rewards and simultaneously trade or invest in other opportunities via their LSTs.

LSTs remove the complexities of traditional staking, eliminating the need to run a validator or select a delegate.


---

# 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://apriori-docs.gitbook.io/apriori-docs/aprmon/what-is-liquid-staking.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.