> For the complete documentation index, see [llms.txt](https://docs.bond.network/guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bond.network/guides/faqs/what-is-the-oracle-problem.md). # What is the oracle problem? The oracle problem, or the 'smart contract connectivity problem', is a challenge faced by blockchains due to their inability to natively interact with external off-chain systems. This arises from the strong security protocols and consensus mechanisms used within the blockchain, which are effective for generating consensus on transactions but hinder access to real-world, subjective data. Blockchains focus on verifying transaction validity while limiting connections to off-chain systems, ensuring the network's continuous operation and deterministic results. To bridge the gap between on-chain and off-chain environments, an 'oracle' is needed; however, this must be highly decentralised to prevent manipulation and ensure the end-to-end security of smart contract execution. --- # 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.bond.network/guides/faqs/what-is-the-oracle-problem.md?ask=&goal= ``` `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.