> 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/deposit-flow.md).

# Deposit Flow

Send any multiple of 32 ETH and become owner of your dedicated Ethereum validators.

The deposit flow of Kiln Onchain dedicated products is straightforward: **user sends any multiple of 32 ETH**, either via a transfer or contract call transaction, to the Dedicated Staking smart contract and becomes owner of dedicated validators.

During this deposit transaction, the Kiln smart contracts deposit on validators previously registered by the Operator of the contracts the user staked on. User funds end up deposited and **segregated** on dedicated validators.

<figure><img src="https://1911902555-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fnye3yqpuOzdfrtWAlwng%2Fuploads%2FbbP7oziEKtcMxPmLvSBY%2Fimage.png?alt=media&amp;token=18933021-9d03-4a3b-9961-3e7340522c70" alt=""><figcaption><p>Deposit Flow overview (v2)<br>Note that on "v1", there is only one contract for both Operator and Partner.</p></figcaption></figure>

Anyone can verify that the validation key deposit data registered by the Operator in the Smart Contract are configured properly (correct signature and withdrawal credentials for example) before depositing, making the flow as trustless and transparent as possible.


---

# 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/deposit-flow.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.