# Oracles In the blockchain context, an *oracle* is a way to bring real-world data onto the blockchain so that it can be used by a decentralized application. Oracles serve many purposes for application builders. For example: * Most stablecoin designs use an oracle to bring in data of the exchange rate of assets, in order to peg their value to a real world currency. * Synthetic assets use oracles as price feeds in order to determine if the underlying cryptocurrency sufficiently collateralizes the debt position. * Prediction markets use oracles to decide the outcome of real world events and determine the payout of the prediction shares. * Decentralized insurance markets use oracles to bring in information about whether a claim is valid or not. Oracle solutions range from centralized and trusted to decentralized and game-theory based. On the centralized end of the spectrum, an oracle could be a single account that has the authority to dictate the real-world data on-chain. On the decentralized end, a [complex game of "chicken"](https://blog.ethereum.org/2014/03/28/schellingcoin-a-minimal-trust-universal-data-feed/) can be played among various staked actors who risk getting slashed if they don't submit the same data as everyone else. Solutions such as [Chainlink](https://polkadot.network/chainlink-reaches-milestone-with-polkadot/) fit somewhere in the middle, where the amount of trust you put into the reporting oracles can be adjusted based on your preferences. A Chainlink [Feed Pallet](https://github.com/smartcontractkit/chainlink-polkadot/blob/master/pallet-chainlink-feed/README.md) was recently released to allow smart contract applications across Polkadot to access price reference data, made available as a Substrate oracle pallet. When using an oracle in your application you should be aware of the benefits and risks that are baked into its specific model. As the Polkadot ecosystem develops and oracle parachains begin to appear, this article will be updated with a comparison of the different solutions and the benefits and drawbacks that each provide. --- # 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.callisto-pirl.com/faq/build/development-guide/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.