> For the complete documentation index, see [llms.txt](https://kernel-protocol.gitbook.io/kernel-protocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kernel-protocol.gitbook.io/kernel-protocol/rewards/rewards-overview.md).

# Rewards Overview

Whilst the underlying assets for ksETH, krETH, kpETH, kUSD and kINDX are restaked on Karak via Kernel Protocol, they will accumulate:

* Karak XP (Karak’s native points)
* Kernel Points (Kernel Protocol’s native points)
* A share of the aggregated yields generated by the underlying assets in their basket.

Meanwhile, the users will be able to deploy their kAssets in further yield-bearing activities as Kernel Protocol builds out its network of utility partners. Liquidity for each asset will be supported by Kernel Protocol’s protocol-owned liquidity, as well as token and points rewards for 3rd-parties providing liquidity.

<br>


---

# 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://kernel-protocol.gitbook.io/kernel-protocol/rewards/rewards-overview.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.