> For the complete documentation index, see [llms.txt](https://docs.liquidfinance.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.liquidfinance.xyz/protocol-features/staking.md).
# Staking
The first feature of the Liquid Finance protocol is Staking.
On the app, the user should navigate to the "Stake" tab. This is where users will deposit the ARCH tokens to receive [sARCH](/protocol-features/sarch.md) tokens in return.
The amount of sARCH tokens received are based on the current sARCH exchange rate which will be displayed in the confirmation message before submitting the transaction.
When a user deposits their ARCH tokens, Liquid Finance will stake them on the Archway Network and will delegate them across the protocols Validator set.
Liquid Finance automatically compounds staking rewards for the user by claiming available rewards and then re-staking them back within the protocol.
This allows holders of sARCH to passively benefit from the compounding of Archway staking rewards without having to perform any other transactions manually.
The projected staking APY is displayed on the app as well, calculated by taking the current Archway staking rewards and projecting a daily compound.
---
# 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://docs.liquidfinance.xyz/protocol-features/staking.md?ask=&goal=
```
`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.