# Oracles Contingent pools require **one data input** - the observed value of the reference asset at the specified expiry time - following pool expiration to determine the payoffs for long and short position tokens. This data is provided by an **oracle** (a.k.a "data provider"), which is **specified by the user at the time of pool creation**. DIVA Protocol has been designed to be oracle agnostic, giving users the freedom to configure the oracle according to their specific setup. This includes the option to use trusted individual accounts (an "EOA"), multisigs, existing decentralized oracle solutions like [Tellor](https://github.com/divaprotocol/diva-protocol-v1/blob/main/README.md#oracles), Chainlink, DIA, as well as custom oracle smart contracts. Refer to the [Oracle Integrations](https://docs.divaprotocol.io/oracle-integrations/overview) section to see the available oracles that can be used for secure and trustless outcome reporting. --- # 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.divaprotocol.io/introduction/what-is-diva-protocol/how-it-works/oracles.md?ask= ``` 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.