> For the complete documentation index, see [llms.txt](https://crosschain-alliance.gitbook.io/hashi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://crosschain-alliance.gitbook.io/hashi/core-concepts/oracles.md). # Oracles Oracles play a pivotal role in Hashi’s ecosystem. They are responsible for relaying block headers and messages between blockchains and validating them in a decentralized manner. Hashi uses multiple oracles to ensure security and avoid relying on a single point of failure. * **Why Multiple Oracles?**\ Trusting a single oracle can introduce vulnerabilities, especially in cross-chain environments where security is critical. Hashi solves this by using multiple oracles, each independently verifying the data. Only when consensus is reached among a majority of these oracles is the data accepted, significantly reducing the risk of manipulation or failure. * **Supported Oracles**\ Hashi is designed to work with various oracles, you can find a list of supported ones [here](/hashi/deployments/oracles.md). These oracles are integrated into Hashi’s framework to ensure compatibility across a range of blockchain environments. * **Oracle Adapters**\ Hashi uses a universal adapter interface, making it easy to add support for new oracles as they emerge. This flexibility allows Hashi to evolve with the ecosystem, accommodating new oracle solutions as needed. --- # 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://crosschain-alliance.gitbook.io/hashi/core-concepts/oracles.md?ask=&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.