> 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="/files/93jAZvl4DR9D0qMSTBHT" 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 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://docs.kiln.fi/v1/kiln-products/onchain/pooled-staking/key-concepts/oracle-reports.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.