> 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/pooled-staking/key-concepts/oracle-reports.md).

# Oracle Reports

The Operator Pool requires offchain information to update pooling metrics like Operator Pool value and exchange rate, to take into account rewards generated by the pool validators.

This data is called an **oracle report and is submitted by whitelisted Oracles** to the Operator Pool smart contract, **once every 24 hours**. If all the Oracle quorum agrees on the same report, this one is processed by the Operator pool.

{% hint style="info" %}
This means that user position values, and exit requests are processed on a 24 hours basis if oracles generate valid reports.
{% endhint %}

<figure><img src="https://1911902555-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fnye3yqpuOzdfrtWAlwng%2Fuploads%2FvPAOy715OtuTjJH4SwP2%2Fimage.png?alt=media&amp;token=8ad9b858-d9a8-4dba-9e43-eab75b82d1bd" alt="" width="356"><figcaption><p>Oracle report processing</p></figcaption></figure>

An oracle report consists of data like total ETH staked, total ETH currently in the protocol Exit Queue, total validators staked, total validators exited and strategy inputs to tell the pool to either accelerate user exits time or increase new validator deposits.

Using this data, Operator pool will perform multiple state transitions to:

* deposit new validators
* answer the exit demand in the exit queue
* compute relevant staking fees
* update the Operator pool exchange rate to take into account new rewards
* exit validators if needed to match the user exit demand in the pool exit queue

You can find the report data and all Operator Pool metrics on [our dune dashboard](https://dune.com/kiln/vpool).


---

# 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/pooled-staking/key-concepts/oracle-reports.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.
