> 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/introduction/key-features.md). # Key Features Hashi introduces a range of features designed to enhance the security and flexibility of cross-chain applications. Here’s a brief overview of what sets Hashi apart: #### **1. Multi-Oracle Validation** Hashi aggregates data from multiple independent oracles to validate block headers and messages. This reduces reliance on a single oracle and increases the security of cross-chain interactions. #### **2. Secure Block Relaying** Hashi relays entire block headers between chains, providing cryptographic proof of blockchain states across multiple networks. This ensures that data being relayed is both secure and verifiable. #### **3. Abstraction Layer for Oracles** Hashi acts as an abstraction layer, allowing you to easily switch between different oracles without being locked into a single provider. This flexibility helps avoid vendor lock-in and future-proofs your application. #### **4. Additive Security Model** With Hashi, security scales as more oracles are added to the validation process. This makes Hashi adaptable to a variety of applications, from low-risk operations to high-value transactions that require additional layers of security. #### **5. Cross-Chain Compatibility** Hashi supports a wide range of blockchains and oracle systems, making it a versatile solution for developers building cross-chain applications. --- # 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/introduction/key-features.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.