# Staking Positions

Users deploy ETH through the partner's integration smart contract, which then forwards the ETH to one or multiple operator pools, depending on the configuration. This approach offers flexibility in structuring staking offerings, such as:

* A single node operator with a 15% end-user fee.
* Three operators with a 10/40/50% allocation and a total 17% end-user fee.

<figure><img src="/files/ONVXYdOcFPMKfqWnsifC" alt=""><figcaption><p>Flow of funds</p></figcaption></figure>

During the staking transaction, the user receives a receipt token representing their staked position within the integration contract. The integration contract, in turn, holds a proportional stake in the Node Operator Pool, based on the amount of ETH deployed through it.

The user's receipt tokens can be either soulbound or transferable (e.g., cToken or aToken), depending on the partner's choice during contract setup. The value of staked positions is determined by the underlying value of the operator pool, with an internal exchange rate that updates daily to reflect validator rewards.  This exchange rate is purely technical and used exclusively between the smart contracts.

Staking fees are automatically calculated by the smart contracts based on the rewards generated, ensuring a seamless experience for the end user, who only deals with net values.


---

# Agent Instructions: 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:

```
GET https://docs.kiln.fi/v1/kiln-products/onchain/pooled-staking/key-concepts/staking-positions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
