> For the complete documentation index, see [llms.txt](https://docs.kiln.fi/v1/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kiln.fi/v1/kiln-products/onchain/deprecated-dedicated-validators/key-concepts/rewards-management.md).
# Rewards Management
Rewards are received by a recipient address controlled by the Smart Contract and can be claimed by the validator owner.
For every validator deposited validators in the Onchain Dedicated smart contracts, there is a deterministically generated Ethereum address, controlled by the contract, set as withdrawal credentials of the validator.
This recipient address receives all the Consensus Layer rewards of the validator it is associated to. It also receives the unstaked amount upon exiting the validator.
Only the registered owner of the validator can claim this recipient address' balance.
Rewards management overview (v2) Note that on "v1", EL Rewards are also segregated with one CL recipient per validator
Upon claiming their rewards, validator owners trigger commission dispatching, a process which sends the net rewards to the validator owner address and the remaining value to the different partners involved in the staking offering.
---
# 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.kiln.fi/v1/kiln-products/onchain/deprecated-dedicated-validators/key-concepts/rewards-management.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.
