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

# Liquid staking

For those who want the flexibility of staking while keeping their assets liquid, we offer liquid staking through our token [rkSOL](https://starke.finance/rksol), built in partnership with Sanctum.

* You can acquire rkSOL tokens through any wallet of Solana aggregator and it represents your staked position in Starke Validator.
* rkSOL accrues rewards automatically, just like native staking, but can also be used across Solana DeFi protocols.
* This ensures your assets remain liquid.

**How rewards are shared:**

* Starke Finance charges 0% validator commission, redistributing 100% of the block rewards proportional to rkSOL’s share of our validator’s total stake.
  * Example: if rkSOL represents 100K SOL out of a total 200K SOL staked, it will receive 50% of all block rewards.
* Sanctum applies a 2.5% protocol fee on top.

With rkSOL, you get the best of both worlds: secure staking rewards, plus the ability to use your staked assets throughout the Solana ecosystem.


---

# 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.starke.finance/products/staking-service/liquid-staking.md?ask=<question>&goal=<user_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.